Re: add timing information to pg_upgrade
Peter Eisentraut <peter@eisentraut.org>
From: Peter Eisentraut <peter@eisentraut.org>
To: Nathan Bossart <nathandbossart@gmail.com>
Cc: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>,
PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2023-08-02T07:15:27Z
Lists: pgsql-hackers
On 01.08.23 17:45, Nathan Bossart wrote:
> The message is too long, so there's no space between it and the "ok"
> message:
>
> Checking for incompatible "aclitem" data type in user tablesok
>
> Instead of altering the messages, we could bump MESSAGE_WIDTH from 60 to
> 62 or 64. Do you prefer that approach?
I think we should change the output format to be more like initdb, like
Doing something ... ok
without horizontally aligning all the "ok"s.
Commits
-
pg_upgrade: Bump MESSAGE_WIDTH.
- 2e7d15ab69d9 16.0 landed
- 9625845532ae 17.0 landed