Re: Track the amount of time waiting due to cost_delay - Mailing list pgsql-hackers

From Bertrand Drouvot
Subject Re: Track the amount of time waiting due to cost_delay
Date
Msg-id Z6w9YNNkliWJzP2e@ip-10-97-1-34.eu-west-3.compute.internal
Whole thread Raw
In response to Re: Track the amount of time waiting due to cost_delay  (Nathan Bossart <nathandbossart@gmail.com>)
List pgsql-hackers
Hi,

On Tue, Feb 11, 2025 at 04:42:26PM -0600, Nathan Bossart wrote:
> 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.

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?

Regards,

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



pgsql-hackers by date:

Previous
From: Ashutosh Bapat
Date:
Subject: EquivalenceClass and custom_read_write
Next
From: John Naylor
Date:
Subject: Re: Fix punctuation errors in PostgreSQL documentation