Re: snapshot recovery conflict despite hot_standby_feedback set to on

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: "Drouvot, Bertrand" <bdrouvot(at)amazon(dot)com>
Cc: PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: snapshot recovery conflict despite hot_standby_feedback set to on
Date: 2022-03-20 06:21:15
Message-ID: CAH2-Wz=VmLCkJeqCRDa3N3Hg9B=P8teV4Sz4aU6OEuLYq=QZ3w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Jan 28, 2022 at 8:17 AM Drouvot, Bertrand <bdrouvot(at)amazon(dot)com> wrote:
> Peter's commit e5d8a99903 added in PG 14 should be fixing this bug (as it makes use of FullTransactionId for the Btree deleted 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's commit e5d8a99903 to be back patched.

Thanks for letting us know about this.

--
Peter Geoghegan

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2022-03-20 08:39:01 BUG #17441: shm_mq receive less data than the sender sends
Previous Message Peter Geoghegan 2022-03-18 17:06:49 Re: BUG #17255: Server crashes in index_delete_sort_cmp() due to race condition with vacuum