public inbox for [email protected]
help / color / mirror / Atom feedFrom: Bertrand Drouvot <[email protected]>
To: Nathan Bossart <[email protected]>
Cc: Magnus Hagander <[email protected]>
Cc: PostgreSQL Developers <[email protected]>
Cc: Michael Paquier <[email protected]>
Cc: Imseih (AWS), Sami <[email protected]>
Subject: Re: Vacuum timing in pg_stat_all_tables
Date: Wed, 12 Mar 2025 10:52:57 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <CABUevEz9v1ZNToPyD98JnWDGZgG=SmPZKkSNzU9hXQ-nGTQF0g@mail.gmail.com>
<Z8cUFTCRFZQIFIYV@nathan>
<[email protected]>
Hi,
On Tue, Mar 04, 2025 at 03:24:26PM +0000, Bertrand Drouvot wrote:
> Like "more stats are always nice" I think that "more explanations in the doc" are
> always nice, so I don't see any reason why not to add this extra explanation.
Attached an attempt to do so.
Note that it does not add extra explanation to "cost-based delay". If we feel the
need we could add a link to "<xref linkend="runtime-config-resource-vacuum-cost"/>"
like it has been done for delay_time in bb8dff9995f.
Regards,
--
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
view thread (7+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: Vacuum timing in pg_stat_all_tables
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox