Re: Track the amount of time waiting due to cost_delay

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>
Cc: Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Masahiro Ikeda <ikedamsh(at)oss(dot)nttdata(dot)com>, "Imseih (AWS), Sami" <simseih(at)amazon(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Robert Haas <robertmhaas(at)gmail(dot)com>
Subject: Re: Track the amount of time waiting due to cost_delay
Date: 2025-02-11 22:42:26
Message-ID: Z6vSUpF0S9DHUxZf@nathan
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Feb 11, 2025 at 08:51:15AM +0000, Bertrand Drouvot wrote:
> On Mon, Feb 10, 2025 at 02:52:46PM -0600, Nathan Bossart wrote:
>> Off-list, I've asked Bertrand to gauge the feasibility of adding this
>> information to the autovacuum logs and to VACUUM/ANALYZE (VERBOSE). IMHO
>> those are natural places to surface this information, and I want to ensure
>> that we're not painting ourselves into a corner with the approach we're
>> using for the progress views.
>
> Yeah, I looked at it and that looks as simmple as 0003 attached (as that's the
> leader that is doing the report in case of parallel workers being used).
>
> 0001 and 0002 remain unchanged.

Thanks. I've committed 0001 and 0002.

--
nathan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2025-02-11 22:48:38 Re: Bump soft open file limit (RLIMIT_NOFILE) to hard limit on startup
Previous Message Daniel Gustafsson 2025-02-11 22:41:51 Re: describe special values in GUC descriptions more consistently