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 1nMth8-0006Rw-E3 for pgsql-bugs@arkaria.postgresql.org; Wed, 23 Feb 2022 15:36:46 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nMth7-0001Da-2a for pgsql-bugs@arkaria.postgresql.org; Wed, 23 Feb 2022 15:36:45 +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 1nMth6-0001DR-EP for pgsql-bugs@lists.postgresql.org; Wed, 23 Feb 2022 15:36:44 +0000 Received: from mail-ej1-x636.google.com ([2a00:1450:4864:20::636]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nMth1-0008AZ-Nn for pgsql-bugs@lists.postgresql.org; Wed, 23 Feb 2022 15:36:43 +0000 Received: by mail-ej1-x636.google.com with SMTP id hw13so52969613ejc.9 for ; Wed, 23 Feb 2022 07:36:39 -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:to :cc:references:from:in-reply-to:content-transfer-encoding; bh=clBnNx+CaTqKHVM8GNEKeCFMM5Q34TSw4VeOCyazUvQ=; b=Zr0YYEFtdMh3IQlP4F18VOYtFkQI66MTKeJ0SN3BpblHK5MWbJvWeTk22X47WHiW2X 36hkeRzcfOZxvdrVigeFbQY4P0DvXMNwi5mX3okyRYn5m8NicNE6iYajjQO7fT9/60z6 4N+2M7pISnE/5QLd9l4wHSh+O135HUvssngNB2o2s4VyFLUGgFflKEkyc7EfLC2G+am8 ShyfK0/g/8fhR1L3G38UJnJLeffofGG9Pqf3BS9C2fqS2+a+phlvTCgbMRmZBRsaon/q ohFReFFzHxiqyjQZXqZCkMe7y2bAdmnSUC2Pz/fZLIT3CaDENski8Zcby+nL7AWlPXMB 7p/w== 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:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=clBnNx+CaTqKHVM8GNEKeCFMM5Q34TSw4VeOCyazUvQ=; b=bkwrab0orTuYW4mTnn3yS347qpbRFQGs5fd2I+0ZAnMJN1fvIF1mcuJN+M+e2p8H19 CCeMYI+BYZFBZ3rAWcqSR5X2Puxfw9LmCcpK27gOzheQbIo7LETSq0WqWYC8LCQ40OT1 rqQFXE21MRSW9Sr5eETqgGNNUnaegNcbc/vHcG6uh2r2Wrxn5wyzjqREhO/r+f30+Rxj 3wKKpjVEVaRNmiXLJEbmh/Pta5nSdQdBvt66jKZb6BlxCCy4ZACXRd+1NYbGMie8GpSr q6WWAP3+NOuedskj4vXGWFUCJe0mxYafi2VK2U/vEnqiDX1fy40sIy+NirFsykl93Zwn 1Mxw== X-Gm-Message-State: AOAM532Q2UYC+Y5C+DTqWhXzyvqyBskrgcmTHds8JsdeyBMCpgukrots 2C2/Ljt0ustaUg0TmhSome5fsJb3VsrccEv2MXF68JirUA7vaiJntg45vPfqitHouS9GUpT2v1+ +eTZt4bwwSZY+ExGXufPqAAESlldxgXJsdVSH0BRqqLLRLMMx/Jt0/USzfO7Gxkh7c3c1uNQ1xC WQb7/CTohEzvEKw5Q41v+gixcSaph+MXdxaNw62hsNk392 X-Google-Smtp-Source: ABdhPJyY3Cx2P8hb2AR8a24FNFdM5sYUSdXxeaGqh5x0+vyeMKDCel2n3AM8ZpsGMm/g8HRoLc2tQA== X-Received: by 2002:a17:906:d9c4:b0:6cc:ecbd:3667 with SMTP id qk4-20020a170906d9c400b006ccecbd3667mr203920ejb.645.1645630596965; Wed, 23 Feb 2022 07:36:36 -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 s15sm4415ejm.70.2022.02.23.07.36.36 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 23 Feb 2022 07:36:36 -0800 (PST) Message-ID: Date: Wed, 23 Feb 2022 16:36:32 +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 To: Victor Yegorov Cc: PostgreSQL mailing lists , Alexander Korotkov References: <17406-71e02820ae79bb40@postgresql.org> <788a0a51-b1e3-3601-5783-3f6488796ec4@enterprisedb.com> From: Tomas Vondra 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 > > 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? regards -- Tomas Vondra EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company