Horton

Re: Doc fix of aggressive vacuum threshold for multixact members storage

Bertrand Drouvot <bertranddrouvot.pg@gmail.com>

View thread View on postgr.es
From: Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
To: John Naylor <johncnaylorls@gmail.com>
Cc: Sami Imseih <samimseih@gmail.com>, Alex Friedman <alexf01@gmail.com>, pgsql-hackers@lists.postgresql.org
Date: 2025-02-26T09:40:08Z
Lists: pgsql-hackers 
Hi,

On Wed, Feb 26, 2025 at 02:04:38PM +0700, John Naylor wrote:
> On Wed, Feb 5, 2025 at 2:23 AM Sami Imseih <samimseih@gmail.com> wrote:
> >
> > I rather we not touch the .c file for this update. It's unlikely the actual
> > computation will change.
> 
> I'm on the fence about putting a hint in the C file, but the
> computation has changed in the past, see commit b4d4ce1d50bbdf , so
> it's a reasonable idea.

Thanks for sharing your thoughts!

I think that the more safeguard we put to avoid code and doc discrepancy the
better (though I agree that this "safeguard" is not perfect but probably better
than none).

Regards,

-- 
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com

Commits

  1. Doc: correct aggressive vacuum threshold for multixact members storage

  2. docs: clarify new aggressive vacuum mode for multi-xacts

  3. Increase threshold for multixact member emergency autovac to 50%.