Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nMtll-0006ba-V3 for pgsql-bugs@arkaria.postgresql.org; Wed, 23 Feb 2022 15:41:33 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nMtlk-0004vH-0B for pgsql-bugs@arkaria.postgresql.org; Wed, 23 Feb 2022 15:41:32 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nMtlj-0004v8-OB for pgsql-bugs@lists.postgresql.org; Wed, 23 Feb 2022 15:41:31 +0000 Received: from mail-ed1-x534.google.com ([2a00:1450:4864:20::534]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nMtlg-0008Cz-Ku for pgsql-bugs@lists.postgresql.org; Wed, 23 Feb 2022 15:41:31 +0000 Received: by mail-ed1-x534.google.com with SMTP id s24so38387409edr.5 for ; Wed, 23 Feb 2022 07:41:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb.com; s=google; h=message-id:date:mime-version:user-agent:subject:content-language :from:to:cc:references:in-reply-to:content-transfer-encoding; bh=yjqufaaKrO59bzH9Apmo6rIk0YgNIZkqQG2JposZS1U=; b=XS/BLtM0ZGFXLBANsmg+QRkerz658Ezr3QFnH+efam5YYgzsBtgebK2qmpFo1mtxqF n8pTVULxTFFj2E/yDuziBeShdL529n9uWNmXnDfYLSAoS3bwBEQrf08Y/S3RHq2A/BTe fTJif3i2CnenV/9ljshXKqCdzVmpWW/HbKHt+EApQlTIx+MOPA+SnbU3ey2WCmIkiI6h pT64vxiuZebMemDM4Rqu9YesvoZbJE7kgPy6JyxTiZ24lzWaOxC2zS0S7SEh3kmtym32 ltaHUi4oRevD1zck9yp67No5RpE1LojJknJ7jHRxt0MgHbPZG0LPyDgH5HepgKI7HsiS 2auA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:from:to:cc:references:in-reply-to :content-transfer-encoding; bh=yjqufaaKrO59bzH9Apmo6rIk0YgNIZkqQG2JposZS1U=; b=2L5AKZXB26K2oIoW0FNtHbfRles58DF0lhl31E7L8kxovAYvaq8KsZzdx1VB4uSf31 QZcQ5iLblvGZpdvX/mRLRaF1yvhV9dDZDLEfScpyf2wcIcbI9DclhMwV26rt8Vg52VHl IK/o983G2jgzVmvM02+3m+bmBViwm11Ar6GcVlt/DBuUDXLv3N9hlEjJQ+EOpxS6wNG5 Qb3fZJdeszvtQQ90kpWCHpKuLKEfBMEiz8Gyh8PLSJsSoHgBRnnxs8GsovGJdyqSc87s jyHUHdg91xRhyJwU2XgQlmU8+0BMjHwoWiWSYFWOXscum80ngEG23R/ZvZitY08ovksU A6hw== X-Gm-Message-State: AOAM530iWIXGiJM8DQa00ETI1/Ez6V26ZmLzJCvw0dBCbT0d7lOEPDzj 2RB2Wnivey15diKI2Yy5sufczYDPrAy3Wg9qWE2eCrmNI1c5S/juBo12GHdRTNZYzGlBdqkQims N2c5DFR9gGg+UE6TpEoH/vO1k4AMkZZuzBpQq+emEbuyJ6GAiy7U3xFGw+ALyRNrS9nTnuXXXU0 ZVRt+TS+vkdu7nB+8aQ/tbnhOkJLjy+VfQDec6pxtECUxQ X-Google-Smtp-Source: ABdhPJzjDfJTG9YV4EMa43XKZZaRFumE9q8zsE5Wz0nE/3uLoJa7u3S2I/muqakp/N5/vRhg73vihw== X-Received: by 2002:a05:6402:138c:b0:413:3d99:f2d6 with SMTP id b12-20020a056402138c00b004133d99f2d6mr2742913edv.189.1645630887519; Wed, 23 Feb 2022 07:41:27 -0800 (PST) Received: from [10.137.0.18] (static-84-42-175-93.net.upcbroadband.cz. [84.42.175.93]) by smtp.gmail.com with ESMTPSA id c6sm4938ejs.130.2022.02.23.07.41.26 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 23 Feb 2022 07:41:27 -0800 (PST) Message-ID: Date: Wed, 23 Feb 2022 16:41:22 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Subject: Re: BUG #17406: Segmentation fault on GiST index after 14.2 upgrade Content-Language: en-US From: Tomas Vondra To: Victor Yegorov Cc: PostgreSQL mailing lists , Alexander Korotkov References: <17406-71e02820ae79bb40@postgresql.org> <788a0a51-b1e3-3601-5783-3f6488796ec4@enterprisedb.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-CLOUD-SEC-AV-Info: enterprisedb,google_mail,monitor X-CLOUD-SEC-AV-Sent: true X-Gm-Spam: 0 X-Gm-Phishy: 0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2/23/22 16:36, Tomas Vondra wrote: >> >> I got approval to send a table with its data and index in the subject >> datafile. >> Taken from the v14 database. >> > > Thanks for the data! I've been able to reproduce the issue (load into > 12, pg_upgrade to 14 and run the query). After bisecting this for a > while, this seems like a bug in PG13 commit > > commit 911e70207703799605f5a0e8aad9f06cff067c63 (HEAD) > Author: Alexander Korotkov > Date: Mon Mar 30 19:17:11 2020 +0300 > > Implement operator class parameters > > ... > > It works fine when upgrading to an earlier build, and crashes since this > commit. I haven't investigated this further, but I guess there's some > thinko in gist_ltree_ops, affecting how we interpret existing indexes. > > Alexander, any ideas? > Sorry, I accidentally used Alexander's old address, so let me CC him with the correct/current one. regards -- Tomas Vondra EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company