Horton

Re: add timing information to pg_upgrade

Nathan Bossart <nathandbossart@gmail.com>

View thread View on postgr.es
From: Nathan Bossart <nathandbossart@gmail.com>
To: Peter Eisentraut <peter@eisentraut.org>
Cc: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2023-08-23T16:35:20Z
Lists: pgsql-hackers

Attachments

On Tue, Aug 22, 2023 at 07:06:23AM -0700, Nathan Bossart wrote:
> On Tue, Aug 22, 2023 at 11:49:33AM +0200, Peter Eisentraut wrote:
>> Let's change MESSAGE_WIDTH to 62 in v16, and then pursue the larger
>> restructuring leisurely.
> 
> Sounds good.  I plan to commit this within the next couple of days.

Here's the patch.  I'm going to run a couple of tests before committing,
but I don't think anything else is required.

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

Commits

  1. pg_upgrade: Bump MESSAGE_WIDTH.