| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Cc: | Nathan Bossart <nathandbossart(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: add timing information to pg_upgrade |
| Date: | 2023-08-01 07:58:24 |
| Message-ID: | AD7ABA5E-E024-46C4-A691-E51E4BFE9A15@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 1 Aug 2023, at 09:45, Peter Eisentraut <peter(at)eisentraut(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Junwang Zhao | 2023-08-01 08:09:32 | [PATCH] [zh_CN.po] fix a typo in simplified Chinese translation file |
| Previous Message | Daniel Gustafsson | 2023-08-01 07:54:34 | Re: [PATCH] psql: \dn+ to show size of each schema (and \dA+ for AMs) |