Re: Track the amount of time waiting due to cost_delay

Bertrand Drouvot <bertranddrouvot.pg@gmail.com>

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-04T10:14:48Z

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 →

Add delay time to VACUUM/ANALYZE (VERBOSE) and autovacuum logs.
- 7720082ae532 18.0 landed
Add cost-based vacuum delay time to progress views.
- bb8dff9995f2 18.0 landed
Add is_analyze parameter to vacuum_delay_point().
- e5b0b0ce1509 18.0 landed
Refresh cost-based delay params more frequently in autovacuum
- 7d71d3dd080b 16.0 cited

Attachments

v16-0001-Introduce-analyze_delay_point.patch (text/x-diff)

Hi,

On Mon, Feb 03, 2025 at 02:05:51PM -0600, Nathan Bossart wrote:
> Barring objections, I am planning to commit this one soon.  I might move
> the addition of analyze_delay_point() to its own patch, but otherwise I
> think it looks good to go.

Yeah, I think that having analyze_delay_point() in its own patch makes sense.
It's done that way in the attached and allows 0002 to be focus on the main
feature.

Regards,

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