Re: BUG #18526: 'UPDATE' inconsistency using index scan with 'NOT EXIST' after upgrading to PostgreSQL 16

From: Christophe Pettus <xof(at)thebuild(dot)com>
To: feliphepozzer(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18526: 'UPDATE' inconsistency using index scan with 'NOT EXIST' after upgrading to PostgreSQL 16
Date: 2024-06-28 17:57:43
Message-ID: F1C7A8AE-A753-4A1F-A027-1B9D25701779@thebuild.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> On Jun 28, 2024, at 10:24, PG Bug reporting form <noreply(at)postgresql(dot)org> wrote:
>
> 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.

Have you tried rebuilding the index to rule out index corruption?

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2024-06-28 19:04:02 Re: BUG #18525: Boolean aggregate functions like EVERY/BOOL_AND should shortcut
Previous Message PG Bug reporting form 2024-06-28 17:24:32 BUG #18526: 'UPDATE' inconsistency using index scan with 'NOT EXIST' after upgrading to PostgreSQL 16