Horton

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

Alex Friedman <alexf01@gmail.com>

View thread View on postgr.es
From: Alex Friedman <alexf01@gmail.com>
To: John Naylor <johncnaylorls@gmail.com>
Cc: Sami Imseih <samimseih@gmail.com>, Bertrand Drouvot <bertranddrouvot.pg@gmail.com>, pgsql-hackers@lists.postgresql.org
Date: 2025-03-04T14:22:45Z
Lists: pgsql-hackers 
>I decided to leave this out, since I just remembered that the most
> likely change is actually to move to 64-bit offsets, as was proposed
> here and has some enthusiastic support:
>
> https://www.postgresql.org/message-id/CACG=ezaWg7_nt-8ey4aKv2w9LcuLthHknwCawmBgEeTnJrJTcw@mail.gmail.com

Thanks for the review and the draft, looks good to me, and I'm okay
with doing this without the code comments. However, it seems like that
thread is just the beginning of wider changes (if they indeed happen),
which may impact these calculations as well, and then maybe a doc
update reminder may come in useful?

Best regards,

Alex Friedman

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%.