Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1sNIMY-007qom-2S
	for pgsql-bugs@arkaria.postgresql.org; Fri, 28 Jun 2024 20:38:30 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1sNIMW-006na4-Dl
	for pgsql-bugs@arkaria.postgresql.org; Fri, 28 Jun 2024 20:38:28 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1sNIMW-006nZv-1C
	for pgsql-bugs@lists.postgresql.org; Fri, 28 Jun 2024 20:38:28 +0000
Received: from sss.pgh.pa.us ([68.162.161.243])
	by makus.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1sNIMT-003bgA-KE
	for pgsql-bugs@lists.postgresql.org; Fri, 28 Jun 2024 20:38:26 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 45SKcNBO2010883;
	Fri, 28 Jun 2024 16:38:23 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Feliphe Pozzer <feliphepozzer@gmail.com>
cc: pgsql-bugs@lists.postgresql.org, Richard Guo <guofenglinux@gmail.com>
Subject: Re: BUG #18526: 'UPDATE' inconsistency using index scan with 'NOT
 EXIST' after upgrading to PostgreSQL 16
In-reply-to: 
 <CAEXQvp3i3tzdm+wUACiB5u+KOyzuUmU1=1wqc_D-6hSSMnqHgQ@mail.gmail.com>
References: <18526-bf89f27cb20d8a18@postgresql.org>
 <2002050.1719602033@sss.pgh.pa.us>
 <CAEXQvp1CmwY3N=e0iyMSO8gPGCM3pb1_+=MDj7caM0iHkgOOWQ@mail.gmail.com>
 <CAEXQvp3i3tzdm+wUACiB5u+KOyzuUmU1=1wqc_D-6hSSMnqHgQ@mail.gmail.com>
Comments: In-reply-to Feliphe Pozzer <feliphepozzer@gmail.com>
	message dated "Fri, 28 Jun 2024 17:32:38 -0300"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2010881.1719607103.1@sss.pgh.pa.us>
Date: Fri, 28 Jun 2024 16:38:23 -0400
Message-ID: <2010882.1719607103@sss.pgh.pa.us>
List-Id: <pgsql-bugs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-bugs@lists.postgresql.org>
List-Owner: <mailto:pgsql-bugs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-bugs>
Archived-At: 
 <https://www.postgresql.org/message-id/2010882.1719607103%40sss.pgh.pa.us>
Precedence: bulk

Feliphe Pozzer <feliphepozzer@gmail.com> writes:
> Hello Tom, I applied the patch you suggested, and it appears that the issue
> has been resolved.

Thanks for following up!  We should have an official fix in August's
minor releases.

			regards, tom lane