Re: add timing information to pg_upgrade - Mailing list pgsql-hackers

From Nathan Bossart
Subject Re: add timing information to pg_upgrade
Date
Msg-id 20230802155915.GA1008426@nathanxps13
Whole thread Raw
In response to Re: add timing information to pg_upgrade  (Peter Eisentraut <peter@eisentraut.org>)
List pgsql-hackers
On Wed, Aug 02, 2023 at 09:14:06AM +0200, Peter Eisentraut wrote:
> On 01.08.23 18:00, Nathan Bossart wrote:
>> One of the main purposes of this thread is to gauge interest.  I'm hoping
>> there are other developers who are interested in reducing
>> pg_upgrade-related downtime, and it seemed like it'd be nice to have
>> built-in functionality for measuring the step times instead of requiring
>> folks to apply this patch every time.  And I think users might also be
>> interested in this information, if for no other reason than to help us
>> pinpoint which steps are taking longer for various workloads.
> 
> If it's just for developers and expert users, perhaps existing shell-level
> functionality like "pg_upgrade | ts" would suffice?

Sure, we could just leave it at that unless anyone sees a reason to bake it
in.

-- 
Nathan Bossart
Amazon Web Services: https://aws.amazon.com



pgsql-hackers by date:

Previous
From: Alena Rybakina
Date:
Subject: Re: POC, WIP: OR-clause support for indexes
Next
From: Tomas Vondra
Date:
Subject: Re: PATCH: Using BRIN indexes for sorted output