Re: Skipping schema changes in publication - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: Skipping schema changes in publication
Date
Msg-id CAKFQuwaEizi5bUD1kM-gn_0Lp-q=O3Axn267jekyehSJtkc=FA@mail.gmail.com
Whole thread
In response to Re: Skipping schema changes in publication  (shveta malik <shveta.malik@gmail.com>)
Responses Re: Skipping schema changes in publication
Re: Skipping schema changes in publication
List pgsql-hackers
On Tuesday, February 10, 2026, shveta malik <shveta.malik@gmail.com> wrote:
>
> The attached v42 version patch has the changes for the same.
>

Thanks, will review.

Publication names are unique within the database.  In check_publications_except_list, the use of “select distinct” when pulling from pg_publication by name is unnecessary.  Furthermore, if we only have a single publication name it is unnecessary to perform the check and thus no need to even run the query.

David J.


+check_publications_except_list(WalReceiverConn *wrconn, List *publications)
+{
+ WalRcvExecResult *res;
+ StringInfoData cmd;
+ TupleTableSlot *slot;
+ Oid tableRow[1] = {TEXTOID};
+ List   *except_publications = NIL;
+
+ initStringInfo(&cmd);
+ appendStringInfoString(&cmd,
+   "SELECT DISTINCT p.pubname\n"
+   "  FROM pg_catalog.pg_publication p\n"
+   " WHERE p.pubname IN (");
+
+ GetPublicationsStr(publications, &cmd, true);
+
+ appendStringInfoString(&cmd,
+   ")\n"
+   "   AND EXISTS (SELECT 1\n"
+   "                 FROM pg_catalog.pg_publication_rel pr\n"
+   "                WHERE pr.prpubid = p.oid\n"
+   "                  AND pr.prexcept IS TRUE)");

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: [Patch] add new parameter to pg_replication_origin_session_setup
Next
From: vignesh C
Date:
Subject: Re: Skipping schema changes in publication