From: Tom Lane <tgl@sss.pgh.pa.us>
To: 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
Date: Fri, 28 Jun 2024 15:13:53 -0400
Message-ID: <2002050.1719602033@sss.pgh.pa.us> (raw)
In-Reply-To: <18526-bf89f27cb20d8a18@postgresql.org>
References: <18526-bf89f27cb20d8a18@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> writes:
> Expected Result: All records that meet the criteria should be updated
> regardless of using index scan or seq scan.
> Actual Result: When PostgreSQL 16 uses index scan, it fails to find and
> update all records. By changing random_page_cost to a value that forces the
> use of seq scan, all records are updated correctly.
I see that the problematic plan involves a Merge Right Anti Join step,
which makes me guess that this is the same bug recently reported in
https://www.postgresql.org/message-id/flat/18522-c7a8956126afdfd0%40postgresql.org
Are you in a position to try the patch posted in that thread?
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, feliphepozzer@gmail.com, guofenglinux@gmail.com
Subject: Re: BUG #18526: 'UPDATE' inconsistency using index scan with 'NOT EXIST' after upgrading to PostgreSQL 16
In-Reply-To: <2002050.1719602033@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox