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

From Nathan Bossart
Subject Re: add timing information to pg_upgrade
Date
Msg-id 20230729211418.GA189222@nathanxps13
Whole thread Raw
In response to Re: add timing information to pg_upgrade  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
Responses Re: add timing information to pg_upgrade
List pgsql-hackers
On Sat, Jul 29, 2023 at 12:17:40PM +0530, Bharath Rupireddy wrote:
> While on this, I noticed a thing unrelated to your patch that there's
> no space between the longest status message of size 60 bytes and ok -
> 'Checking for incompatible "aclitem" data type in user tablesok
> 23.932 ms'. I think MESSAGE_WIDTH needs to be bumped up - 64 or more.

Good catch.  I think I'd actually propose just removing "in user tables" or
the word "incompatible" from these messages to keep them succinct.

-- 
Nathan Bossart
Amazon Web Services: https://aws.amazon.com



pgsql-hackers by date:

Previous
From: Isaac Morland
Date:
Subject: Re: Faster "SET search_path"
Next
From: Nathan Bossart
Date:
Subject: Re: should frontend tools use syncfs() ?