From: Peter Eisentraut <peter@eisentraut.org>
To: Nathan Bossart <nathandbossart@gmail.com>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: add timing information to pg_upgrade
Date: Wed, 2 Aug 2023 09:14:06 +0200
Message-ID: <4fe4c4d2-e87d-fd6d-0866-a453a2d4c32a@eisentraut.org> (raw)
In-Reply-To: <20230801160006.GB723589@nathanxps13>
References: <20230727235134.GA3658499@nathanxps13>
<204e3982-78be-7550-fdb3-063ecd368f1f@eisentraut.org>
<AD7ABA5E-E024-46C4-A691-E51E4BFE9A15@yesql.se>
<20230801160006.GB723589@nathanxps13>
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?
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: peter@eisentraut.org, nathandbossart@gmail.com, daniel@yesql.se
Subject: Re: add timing information to pg_upgrade
In-Reply-To: <4fe4c4d2-e87d-fd6d-0866-a453a2d4c32a@eisentraut.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox