Re: Doc fix of aggressive vacuum threshold for multixact members storage - Mailing list pgsql-hackers

From Bertrand Drouvot
Subject Re: Doc fix of aggressive vacuum threshold for multixact members storage
Date
Msg-id Z77heCxm+vxJafQB@ip-10-97-1-34.eu-west-3.compute.internal
Whole thread Raw
In response to Re: Doc fix of aggressive vacuum threshold for multixact members storage  (John Naylor <johncnaylorls@gmail.com>)
List 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



pgsql-hackers by date:

Previous
From: Maxim Orlov
Date:
Subject: Re: Spinlock can be released twice in procsignal.c
Next
From: Richard Guo
Date:
Subject: Re: Anti join confusion