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

From Daniel Gustafsson
Subject Re: add timing information to pg_upgrade
Date
Msg-id AD7ABA5E-E024-46C4-A691-E51E4BFE9A15@yesql.se
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 1 Aug 2023, at 09:45, Peter Eisentraut <peter@eisentraut.org> wrote:
> On 28.07.23 01:51, Nathan Bossart wrote:

>> This information can be used to better understand where the time is going
>> and to validate future improvements.
>
> But who would use that, other than, you know, you, right now?
>
> I think the pg_upgrade output is already too full with not-really-actionable information (like most of the above
"Checking..." are not really interesting for a regular user). 

Maybe if made opt-in with a --debug option, or even a compiler option for
enabling only in specialized debugging builds?

--
Daniel Gustafsson




pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: [PATCH] psql: \dn+ to show size of each schema (and \dA+ for AMs)
Next
From: Junwang Zhao
Date:
Subject: [PATCH] [zh_CN.po] fix a typo in simplified Chinese translation file