Horton

Re: Track the amount of time waiting due to cost_delay

Masahiro Ikeda <ikedamsh@oss.nttdata.com>

View thread
From: Masahiro Ikeda <ikedamsh@oss.nttdata.com>
To: Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
Cc: Nathan Bossart <nathandbossart@gmail.com>, "Imseih (AWS), Sami" <simseih@amazon.com>, Masahiko Sawada <sawada.mshk@gmail.com>, pgsql-hackers@lists.postgresql.org, Robert Haas <robertmhaas@gmail.com>
Date: 2024-12-09T09:21:21Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Add delay time to VACUUM/ANALYZE (VERBOSE) and autovacuum logs.

  2. Add cost-based vacuum delay time to progress views.

  3. Add is_analyze parameter to vacuum_delay_point().

  4. Refresh cost-based delay params more frequently in autovacuum

On 2024-12-06 18:31, Bertrand Drouvot wrote:
> Hi,
> 
> On Thu, Dec 05, 2024 at 10:43:51AM +0000, Bertrand Drouvot wrote:
>> Yeah, people would likely use this new field to monitor long running 
>> vacuum.
>> Long enough that this error should be acceptable. Do you agree?
> 
> OTOH, adding the 100% accuracy looks as simple as v9-0002 attached 
> (0001 is
> same as for v8), so I think we should provide it.

Thanks! The patch looks good to me.

Regards,
-- 
Masahiro Ikeda
NTT DATA CORPORATION