Re: pg_upgrade and logical replication

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, vignesh C <vignesh21(at)gmail(dot)com>, "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Peter Smith <smithpb2250(at)gmail(dot)com>, Julien Rouhaud <rjuju123(at)gmail(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_upgrade and logical replication
Date: 2024-07-25 03:16:51
Message-ID: ZqHDo7cUbdA3WE1j@nathan
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jul 25, 2024 at 08:43:03AM +0530, Amit Kapila wrote:
>> Shall we close the open items?
>
> Sorry for the typo. There is only one open item corresponding to this:
> "Subscription and slot information retrieval inefficiency in
> pg_upgrade" which according to me should be closed after your commit.

Oops, I forgot to do that. I've moved it to the "resolved before 17beta3"
section.

--
nathan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message John Naylor 2024-07-25 03:18:15 Re: Make tuple deformation faster
Previous Message SAMEER KUMAR 2024-07-25 03:13:39 Adding clarification to description of IPC wait events XactGroupUpdate and ProcArrayGroupUpdate