Horton

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

vignesh C <vignesh21@gmail.com>

View thread View on postgr.es
From: vignesh C <vignesh21@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Dilip Kumar <dilipbalaut@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2022-08-08T06:40:53Z
Lists: pgsql-hackers

Attachments

On Sat, Mar 12, 2022 at 1:29 PM vignesh C <vignesh21@gmail.com> wrote:
>
> On Fri, Dec 3, 2021 at 3:21 PM vignesh C <vignesh21@gmail.com> wrote:
> >
> > On Fri, Dec 3, 2021 at 1:13 PM Michael Paquier <michael@paquier.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

Commits

  1. Invalidate pgoutput's replication-decisions cache upon schema rename.

  2. Add wait_for_subscription_sync for TAP tests.

  3. Unify PostgresNode's new() and get_new_node() methods