From: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Invalidate pgoutput's replication-decisions cache upon schema re
Date: Fri, 06 Jan 2023 16:12:13 +0000
Message-ID: <E1pDpKH-002LwH-IJ@gemulon.postgresql.org> (raw)
Invalidate pgoutput's replication-decisions cache upon schema rename.
A schema rename should cause reporting the new qualified names of
tables to logical replication subscribers, but that wasn't happening.
Flush the RelationSyncCache to make it happen.
(If you ask me, the new test case shows that the behavior in this area
is still pretty dubious, but apparently it's operating as designed.)
Vignesh C
Discussion: https://postgr.es/m/CALDaNm32vLRv5KdrDFeVC-CU+4Wg1daA55hMqOxDGJBzvd76-w@mail.gmail.com
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/cd4b2334db4980bbf86a8ba1d446db17e62ca342
Modified Files
--------------
src/backend/replication/pgoutput/pgoutput.c | 25 ++++++++---
src/test/subscription/t/100_bugs.pl | 65 ++++++++++++++++++++++++++++-
2 files changed, 84 insertions(+), 6 deletions(-)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-committers@postgresql.org
Cc: tgl@sss.pgh.pa.us
Subject: Re: pgsql: Invalidate pgoutput's replication-decisions cache upon schema re
In-Reply-To: <E1pDpKH-002LwH-IJ@gemulon.postgresql.org>
References: <E1pDpKH-002LwH-IJ@gemulon.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox