Re: Logical replication - schema change not invalidating the relation cache

From: vignesh C <vignesh21(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Dilip Kumar <dilipbalaut(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Logical replication - schema change not invalidating the relation cache
Date: 2022-08-08 06:40:53
Message-ID: CALDaNm1p29eNkCwAiPk=CDAb29itNOinPVkntc5fQ2UO+WYwoQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Mar 12, 2022 at 1:29 PM vignesh C <vignesh21(at)gmail(dot)com> wrote:
>
> On Fri, Dec 3, 2021 at 3:21 PM vignesh C <vignesh21(at)gmail(dot)com> wrote:
> >
> > On Fri, Dec 3, 2021 at 1:13 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> > >
> > > On Thu, Aug 26, 2021 at 09:00:39PM +0530, vignesh C wrote:
> > > > The previous patch was failing because of the recent test changes made
> > > > by commit 201a76183e2 which unified new and get_new_node, attached
> > > > patch has the changes to handle the changes accordingly.
> > >
> > > Please note that the CF app is complaining about this patch, so a
> > > rebase is required. I have moved it to next CF, waiting on author,
> > > for now.
> >
> > Thanks for letting me know, I have rebased it on top of HEAD, the
> > attached v2 version has the rebased changes.
>
> The patch was not applying on top of the HEAD, attached v3 version
> which has the rebased changes.

The patch needed to be rebased on top of HEAD because of commit
"0c20dd33db1607d6a85ffce24238c1e55e384b49", attached a rebased v3
version for the changes of the same.

Regards,
Vignesh

Attachment Content-Type Size
v3-0001-Fix-for-invalidating-logical-replication-relation.patch application/octet-stream 5.9 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message John Naylor 2022-08-08 06:46:48 Re: optimize lookups in snapshot [sub]xip arrays
Previous Message Bharath Rupireddy 2022-08-08 06:29:19 Re: pg_receivewal fail to streams when the partial file to write is not fully initialized present in the wal receiver directory