Horton

Re: Track the amount of time waiting due to cost_delay

Bertrand Drouvot <bertranddrouvot.pg@gmail.com>

View thread
From: Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
To: Nathan Bossart <nathandbossart@gmail.com>
Cc: Dilip Kumar <dilipbalaut@gmail.com>, Masahiro Ikeda <ikedamsh@oss.nttdata.com>, "Imseih (AWS), Sami" <simseih@amazon.com>, Masahiko Sawada <sawada.mshk@gmail.com>, pgsql-hackers@lists.postgresql.org, Robert Haas <robertmhaas@gmail.com>
Date: 2025-02-13T07:02:10Z
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

Hi,

On Wed, Feb 12, 2025 at 11:13:13AM -0600, Nathan Bossart wrote:
> On Wed, Feb 12, 2025 at 06:19:12AM +0000, Bertrand Drouvot wrote:
> > Thanks! Regarding 0003 I think it's ok to keep it in this thread (and not
> > create a dedicated one), as it still fits well with $SUBJECT (and the folks 
> > interested in are probably already part of this thread). Sounds good to you?
> 
> Yup.  Here is what I have staged for commit.

Thanks! I can see that those changes have been made:

1. The order in the output (it's now displayed before "track_io_timing")

2. The "and" addition in the doc 

All of the above is fine by me.

> I'll create a commifest entry
> for this one and give it a couple days for review, but this seems pretty
> straightforward.

Yup, sounds like a plan, thanks!

Regards,

-- 
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com