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

From Bharath Rupireddy
Subject Re: add timing information to pg_upgrade
Date
Msg-id CALj2ACVn0DU_xJ+i1GmpSw+QcX-n2JcHG_1M-R7omimwqqyN+w@mail.gmail.com
Whole thread Raw
In response to Re: add timing information to pg_upgrade  (Peter Eisentraut <peter@eisentraut.org>)
Responses Re: add timing information to pg_upgrade
List pgsql-hackers
On Wed, Aug 2, 2023 at 12:44 PM Peter Eisentraut <peter@eisentraut.org> 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?

Interesting. I had to install moreutils package to get ts. And,
something like ts command may or may not be available on all
platforms. Moreover, the ts command gives me the timestamps for each
of the messages printed, so an extra step is required to calculate the
time taken for an operation. I think it'd be better if pg_upgrade can
calculate the time taken for each operation, and I'm okay if it is an
opt-in feature with --verbose option.

[1]
Aug 02 07:44:17 Sync data directory to disk                                 ok
Aug 02 07:44:17 Creating script to delete old cluster                       ok
Aug 02 07:44:17 Checking for extension updates                              ok

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



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: cataloguing NOT NULL constraints
Next
From: Amit Kapila
Date:
Subject: Re: [PATCH] Reuse Workers and Replication Slots during Logical Replication