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 1nNLUU-0006Sq-Sf for pgsql-bugs@arkaria.postgresql.org; Thu, 24 Feb 2022 21:17:34 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nNLUT-0000Lb-DE for pgsql-bugs@arkaria.postgresql.org; Thu, 24 Feb 2022 21:17:33 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nNLUT-0000LS-58 for pgsql-bugs@lists.postgresql.org; Thu, 24 Feb 2022 21:17:33 +0000 Received: from mail-ej1-x635.google.com ([2a00:1450:4864:20::635]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nNLUQ-0003lu-N0 for pgsql-bugs@lists.postgresql.org; Thu, 24 Feb 2022 21:17:32 +0000 Received: by mail-ej1-x635.google.com with SMTP id a8so6956170ejc.8 for ; Thu, 24 Feb 2022 13:17:30 -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=cjGKwNfF+41OIKYC8ExDkv/BNEASyhsBWHtXAAEZg7g=; b=jQE4GRWB2j0V6I+CIMepfMi75n4QOGqdeV/3tPo4q2CCNghEoMUWlMdqf7Xatl5sPo hrfVtDl/EgO/Oa7DgxYXF0NtXCR+lGVTPTTG1gAlQslP2R6Uw9R28rqwXX7bMJAfXgia nK2Izqvs3PIhwkbZ+VRL3r1hMPJCjNOQGopUFtwa4d0XiYaPsZjGalo8bd+CfefmOt+1 i028d2P+XAfImbe12cgObDcwNAh6mObdX6IxKqoTrpjSzYf5gf/sWxM969w+cPEh3qaG x0v09H1hS5akczzCArtG1gZru5E6vX/3yhdQZVwiYJMHLp1xEPvobRB0BURiLdsnPvja 4UTw== 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=cjGKwNfF+41OIKYC8ExDkv/BNEASyhsBWHtXAAEZg7g=; b=wdVrI7Yphva0FT5elCAAN5L81B21ktGVE2H1gsgr6P1VvjIhvQ6SLcgsz3bh9U2/AG xkJAdz/4OjtX8j1gciVLiH/6E5Nss3nRuTe7Kx5JqybuhfCbTv1TpnPYtU0hmS4ewYcL PSkD3jTyKZC0ZnQ7QTrdh/BUiHufehEx/Pc0hhveFejjWvHxH0zmUORzAAu5XfZP7KWe zG8bf8hca5S2DLlQkhHULX+HwRtSPCBcZafILRLd9e8/4mPC6FAM2ewytVHudgalI1F0 FElyItkly88fD8vCU2UYNl3+DqLd3rbiBtODsm9awdIe2c6kf14RRbroVDmZ7HzRWUZJ 4gTw== X-Gm-Message-State: AOAM532/C0wEZogEvfFCEXx9cr0ck86TSQMNgBAvN4Ah1GkOdPgQFrdv e7QwMQdewfEdF/vYnUGUHqi/X/+tdtuEw2MVMD6CX/euf4Y5sjONrjNDbFVPHZMLRMWJe0IoT97 nJdkluijSLov8zQvcvAKZtr/uOlku2+ii+4/EtaW1e0bYXq8Ly3KVkfCAoagiZ0GonvVWzu6llh qx/vYwdGeDYhVvKAVgyg0gnQVjITfE4yU5jqVPYViexwl0 X-Google-Smtp-Source: ABdhPJxBlQ9ao+SR9KPR89pEeaPBPiu2g0BZCGSBLYfWyr1WOmRYkOGY3aG48Stjh7l3XEwnIHOVtA== X-Received: by 2002:a17:906:5804:b0:6ce:3f17:bf35 with SMTP id m4-20020a170906580400b006ce3f17bf35mr3712050ejq.346.1645737449378; Thu, 24 Feb 2022 13:17:29 -0800 (PST) Received: from [10.137.0.19] (ip-86-49-251-241.net.upcbroadband.cz. [86.49.251.241]) by smtp.gmail.com with ESMTPSA id i13-20020a170906114d00b006d5aca9fc81sm192152eja.87.2022.02.24.13.17.28 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 24 Feb 2022 13:17:29 -0800 (PST) Message-ID: <6bc7e8a7-382f-9d8d-8b8d-9c6607f7fa15@enterprisedb.com> Date: Thu, 24 Feb 2022 22:17:27 +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> <14ac4567-3285-f549-67df-debaeab7719f@enterprisedb.com> <5cd74597-f555-d4e1-4dc2-d399180bb8cc@enterprisedb.com> In-Reply-To: <5cd74597-f555-d4e1-4dc2-d399180bb8cc@enterprisedb.com> 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/24/22 19:36, Tomas Vondra wrote: > > ... > > Attached is a patch that fixes this, but I wonder what will happen to > new indexes created on 13+. Will check. > Unfortunately, the patch fixes indexes built on PG12, but it also breaks indexes created after pg_upgrade :-( I'm not sure if a good solution even exists, because we can't really distinguish those indexes. It only affects ltree_gist, though, and we didn't get any other reports so far, so either few people are using it or have not upgraded yet. I've created a thread on pgsql-hackers [1], where it might get more attention from other developers. Maybe they'll have a better idea on how to fix this. regards [1] https://www.postgresql.org/message-id/d80e0a55-6c3e-5b26-53e3-3c4f973f737c%40enterprisedb.com -- Tomas Vondra EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company