| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
| Cc: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: add timing information to pg_upgrade |
| Date: | 2023-08-02 07:15:27 |
| Message-ID: | 68c0092c-2d81-68a4-04c5-920bc428feac@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bharath Rupireddy | 2023-08-02 07:32:53 | Re: add timing information to pg_upgrade |
| Previous Message | Peter Eisentraut | 2023-08-02 07:14:06 | Re: add timing information to pg_upgrade |