Re: optimizing pg_upgrade's once-in-each-database steps

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Nathan Bossart <nathandbossart(at)gmail(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: optimizing pg_upgrade's once-in-each-database steps
Date: 2024-07-25 09:42:55
Message-ID: 6633BF53-C2AC-4438-A1B5-24D4AF51C221@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 25 Jul 2024, at 04:58, Nathan Bossart <nathandbossart(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hayato Kuroda (Fujitsu) 2024-07-25 09:58:03 RE: Parallel heap vacuum
Previous Message Daniel Gustafsson 2024-07-25 09:36:57 Re: improve ssl error code, 2147483650