Re: Parallel TID Range Scan returns wrong results on rescan

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Parallel TID Range Scan returns wrong results on rescan
Date: 2026-10-16 03:50:57
Message-ID: CAApHDvr3Ce1h=S55M84yGjRb0=T3RFwNR-oRfdrPPBomuueNRQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 16 Oct 2026 at 08:54, Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com> wrote:
> The attached patch resets both fields to InvalidBlockNumber in
> table_block_parallelscan_reinitialize(), and adds a test that fails
> without the fix.

Thanks. I've pushed that one to master and wrote an adapted version
for v19's lack of atomics for those fields.

David

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message yangboyu 2026-10-16 03:51:28 回复：logical decoding: skip unnecessary snapshot distribution.
Previous Message Manu 2026-10-16 03:39:54 Re: [PG19] Promotion hangs behind a backend blocked on a stuck client