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 CANWCAZYeHnBiC32cFTmr-WKmoJ2_qCDQt4yNgL17VvpR+SNqxA@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 Saturday, July 27, 2024, Melanie Plageman <melanieplageman@gmail.com> wrote:

Yes, the only thing that is important is having two rounds of index
vacuuming and having one tuple with a value matching my cursor
condition before the first index vacuum and one after. What do you
mean update only the last few tuples though?

I meant we could update tuples with the highest offsets on each page. That would then lead to longer arrays of bitmaps to store offsets during vacuum. Lowering the minimum memory setting is easier to code and reason about, however. 

pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: why is pg_upgrade's regression run so slow?
Next
From: David Rowley
Date:
Subject: Re: Fix overflow in pg_size_pretty