Re: Vacuum ERRORs out considering freezing dead tuples from before OldestXmin - Mailing list pgsql-hackers

From John Naylor
Subject Re: Vacuum ERRORs out considering freezing dead tuples from before OldestXmin
Date
Msg-id CANWCAZa4keHBSm+Hae9JF_Nck7cc_ybPOg6EMTyzL3k=UWb+gw@mail.gmail.com
Whole thread Raw
In response to Re: Vacuum ERRORs out considering freezing dead tuples from before OldestXmin  (Melanie Plageman <melanieplageman@gmail.com>)
List pgsql-hackers
On Thu, Aug 1, 2024 at 4:47 AM Melanie Plageman
<melanieplageman@gmail.com> wrote:
>
> On Wed, Jul 31, 2024 at 4:38 PM Peter Geoghegan <pg@bowt.ie> wrote:
> >
> > On Thu, Jun 20, 2024 at 7:42 PM Melanie Plageman
> > <melanieplageman@gmail.com> wrote:
> > > In back branches starting with 14, failing to remove tuples older than
> > > OldestXmin during pruning caused vacuum to infinitely loop in
> > > lazy_scan_prune(), as investigated on this [1] thread.
> >
> > Shouldn't somebody remove the entry that we have for this issue under
> > https://wiki.postgresql.org/wiki/PostgreSQL_17_Open_Items#Older_bugs_affecting_stable_branches?
>
> Thanks for the reminder. Done!

Hi, are we still lacking test coverage for this on v17 and up?

--
John Naylor
Amazon Web Services



pgsql-hackers by date:

Previous
From: Perumal Raj
Date:
Subject: Logical Replication slot disappeared after promote Standby
Next
From: Tatsuo Ishii
Date:
Subject: Re: [PATCH] Proposal: Improvements to PDF stylesheet and table column widths