Re: add timing information to pg_upgrade

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Peter Eisentraut <peter(at)eisentraut(dot)org>
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-23 16:35:20
Message-ID: 20230823163520.GA1064471@nathanxps13
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

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:

Attachment Content-Type Size
0001-bump-MESSAGE_WIDTH-to-62.patch text/x-diff 671 bytes

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2023-08-23 16:36:01 Re: PG 16 draft release notes ready
Previous Message Ashutosh Bapat 2023-08-23 16:15:44 Re: Oversight in reparameterize_path_by_child leading to executor crash