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

From: Sami Imseih <samimseih(at)gmail(dot)com>
To: Alex Friedman <alexf01(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Doc fix of aggressive vacuum threshold for multixact members storage
Date: 2025-02-03 16:59:07
Message-ID: CAA5RZ0sRnmpu4zR2bQ_v+m=4aQPK5jvpy+Ra8azVcxZLOhVfug@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thanks for the patch!

This does look like a documentation bug indeed.

I have a few comments:

1/ Remove this as
"(50% of the maximum, which is about 20GB),"

[1] tried to avoid explaining this level of detail, and I
agree with that.

2/ c/"about 10GB"/"10GB" the "about" does not seem necessary here.

[1] https://www.postgresql.org/message-id/flat/162395467510.686.11947486273299446208%40wrigleys.postgresql.org

Regards

Sami
Amazon Web Services (AWS)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Melanie Plageman 2025-02-03 17:19:32 Re: Eagerly scan all-visible pages to amortize aggressive vacuum
Previous Message Michail Nikolaev 2025-02-03 16:57:05 Re: new commitfest transition guidance