Re: optimizing pg_upgrade's once-in-each-database steps - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: optimizing pg_upgrade's once-in-each-database steps
Date
Msg-id 6633BF53-C2AC-4438-A1B5-24D4AF51C221@yesql.se
Whole thread Raw
In response to Re: optimizing pg_upgrade's once-in-each-database steps  (Nathan Bossart <nathandbossart@gmail.com>)
Responses Re: optimizing pg_upgrade's once-in-each-database steps
List pgsql-hackers
> On 25 Jul 2024, at 04:58, Nathan Bossart <nathandbossart@gmail.com> wrote:
>
> On Mon, Jul 22, 2024 at 03:07:10PM -0500, Nathan Bossart wrote:
>> Here is a new patch set.  I've included the latest revision of the patch to
>> fix get_db_subscription_count() from the other thread [0] as 0001 since I
>> expect that to be committed soon.  I've also moved the patch that moves the
>> "live_check" variable to "user_opts" to 0002 since I plan on committing
>> that sooner than later, too.  Otherwise, I've tried to address all feedback
>> provided thus far.
>
> Here is just the live_check patch.  I rebased it, gave it a commit message,
> and fixed a silly mistake.  Barring objections or cfbot indigestion, I plan
> to commit this within the next couple of days.

LGTM

--
Daniel Gustafsson




pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: improve ssl error code, 2147483650
Next
From: "Hayato Kuroda (Fujitsu)"
Date:
Subject: RE: Parallel heap vacuum