Re: Vacuum ERRORs out considering freezing dead tuples from before OldestXmin

From: Melanie Plageman <melanieplageman(at)gmail(dot)com>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Noah Misch <noah(at)leadboat(dot)com>
Subject: Re: Vacuum ERRORs out considering freezing dead tuples from before OldestXmin
Date: 2024-07-31 21:46:54
Message-ID: CAAKRu_YvXQX=5N67RoNS_QstcB5Ba-_B-DNyWJy7oizQgT3P7Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jul 31, 2024 at 4:38 PM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
>
> On Thu, Jun 20, 2024 at 7:42 PM Melanie Plageman
> <melanieplageman(at)gmail(dot)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!

- Melanie

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Sutou Kouhei 2024-07-31 21:49:49 Re: Fixing backslash dot for COPY FROM...CSV
Previous Message Nathan Bossart 2024-07-31 21:43:02 Re: Popcount optimization using AVX512