Re: snapshot recovery conflict despite hot_standby_feedback set to on - Mailing list pgsql-bugs

From Peter Geoghegan
Subject Re: snapshot recovery conflict despite hot_standby_feedback set to on
Date
Msg-id CAH2-Wz=VmLCkJeqCRDa3N3Hg9B=P8teV4Sz4aU6OEuLYq=QZ3w@mail.gmail.com
Whole thread Raw
In response to snapshot recovery conflict despite hot_standby_feedback set to on  ("Drouvot, Bertrand" <bdrouvot@amazon.com>)
List pgsql-bugs
On Fri, Jan 28, 2022 at 8:17 AM Drouvot, Bertrand <bdrouvot@amazon.com> wrote:
> Peter's commit e5d8a99903 added in PG 14 should be fixing this bug (as it makes use of FullTransactionId for the
Btreedeleted page) even if the original intend was to avoid "leaking" of Btree deleted pages.
 
>
> Recommendation:
>
> Given the fact that the bug described here is occurring at very rare circumstances we don't think this is worth
Peter'scommit e5d8a99903 to be back patched.
 

Thanks for letting us know about this.

-- 
Peter Geoghegan



pgsql-bugs by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: BUG #17255: Server crashes in index_delete_sort_cmp() due to race condition with vacuum
Next
From: PG Bug reporting form
Date:
Subject: BUG #17441: shm_mq receive less data than the sender sends