Re: pg_rewind and hint bits leads to visibility corruption

From: shihao zhong <zhong950419(at)gmail(dot)com>
To: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
Cc: Jan Nidzwetzki <jan(at)planetscale(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org, Tom Pang <tom(at)planetscale(dot)com>
Subject: Re: pg_rewind and hint bits leads to visibility corruption
Date: 2026-11-21 18:51:38
Message-ID: CAGRkXqQU6y+-mKcnGRLe=G0xwygMswxu9cczQVr8VyPreLraUw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi Jan,

One correction to my last mail. pd_prune_xid does depend on a
transaction outcome, but a stale value is harmless.

The attached diff brings the first scan after promotion from 85 MB back
to 7.7 kB and your test is still good

Thanks,
Shihao

Attachment Content-Type Size
nocfbot-v1-suggestions.txt text/plain 2.5 KB

In response to

Browse pgsql-bugs by date

  From Date Subject
Previous Message shihao zhong 2026-11-21 17:56:23 Re: pg_rewind and hint bits leads to visibility corruption