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-24 17:23:35
Message-ID: 20230824172335.GA1592177@nathanxps13.lan
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Aug 23, 2023 at 09:35:20AM -0700, Nathan Bossart wrote:
> 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.

committed

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ranier Vilela 2023-08-24 17:46:42 Avoid a possible overflow (src/backend/utils/sort/logtape.c)
Previous Message Dave Cramer 2023-08-24 16:54:34 Re: PostgreSQL 16 release announcement draft