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

From: Melanie Plageman <melanieplageman(at)gmail(dot)com>
To: John Naylor <johncnaylorls(at)gmail(dot)com>
Cc: Peter Geoghegan <pg(at)bowt(dot)ie>, 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: 2025-06-12 22:23:11
Message-ID: CAAKRu_bivVarAaATYTL9bKHjcsfzyPkOt1yzUACbM_X_FOQecA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jun 12, 2025 at 4:11 AM John Naylor <johncnaylorls(at)gmail(dot)com> wrote:
>
> Hi, are we still lacking test coverage for this on v17 and up?

Yep. I have been procrastinating on swapping all this back into my
brain. I'll start working on it today. I think I just take the
reverted test and make the UPDATE a DELETE, set mwm 64 kB, make the
table have 9000 rows and maybe consider using your:

delete from test where ctid::text like '%,2__)';

But, unfortunately, to be able to commit it, I'll have to remember
everything about this. I'll begin now...

- Melanie

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dimitrios Apostolou 2025-06-12 23:00:26 Re: [PING] [PATCH v2] parallel pg_restore: avoid disk seeks when jumping short distance forward
Previous Message Jeff Davis 2025-06-12 21:20:11 Re: pg_dump --with-* options