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

From: Sami Imseih <samimseih(at)gmail(dot)com>
To: Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>
Cc: Alex Friedman <alexf01(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Doc fix of aggressive vacuum threshold for multixact members storage
Date: 2025-02-21 14:14:13
Message-ID: CAA5RZ0vSXSEupPyVpgD6yynHS15Uq2=gY5B-x7u6PmoKWqEeUQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Maybe we could also add a comment in multixact.c to update the doc accordingly if
> the computation changes? (I think that will be easy to miss).

Thanks for the comments!

I rather we not touch the .c file for this update. It's unlikely the actual
computation will change.

Regards,

Sami Imseih
Amazon Web Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2025-02-21 14:26:55 Re: Extend postgres_fdw_get_connections to return remote backend pid
Previous Message Suraj Kharage 2025-02-21 14:10:44 Re: Support for NO INHERIT to INHERIT state change with named NOT NULL constraints