Re: Parallel TID Range Scan returns wrong results on rescan

From: shihao zhong <zhong950419(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>, David Rowley <dgrowleyml(at)gmail(dot)com>
Subject: Re: Parallel TID Range Scan returns wrong results on rescan
Date: 2026-10-16 03:11:13
Message-ID: CAGRkXqQOdAhWm=+=WHyPpWhTDrbAw2xQTBA_Bn_g=82sCRiF0A@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Zsolt,

Thanks for working on this.

v1 looks good to me. I can reproduce it on master and the patch
fixes it.

I think reinitialize is the right place for the fix. Before 19,
phs_startblock did not depend on the query, so keeping it across
rescans was fine.

Thanks,
Shihao

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message shihao zhong 2026-10-16 03:13:03 Re: Improving scalability of Parallel Bitmap Heap/Index Scan
Previous Message Chao Li 2026-10-16 03:10:13 Re: [PATCH] Doc fix for autovacuum_max_parallel_workers