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

From Andrei Lepikhov
Subject Re: Skipping schema changes in publication
Date
Msg-id 3f2555bf-8deb-4164-a888-e7a52447c79b@gmail.com
Whole thread Raw
In response to Re: Skipping schema changes in publication  (shveta malik <shveta.malik@gmail.com>)
List pgsql-hackers
On 26/2/26 05:56, shveta malik wrote:
> On Thu, Feb 26, 2026 at 8:26 AM Amit Kapila <amit.kapila16@gmail.com> wrote:
>> On Wed, Feb 25, 2026 at 7:09 PM Andrei Lepikhov <lepihov@gmail.com> wrote:
> pg_publication_rel will not contain any regular table entries for a
> given pubid when EXCEPT is used. Except is for ALL-TABLES pub alone
> for which base-table entries are stored in pg_publication_tables. Thus
> for an EXCEPT pub, anything we fetch from pg_publication_rel using the
> pubid index
> would necessarily be an EXCEPT entry. The scenario where we retrieve,
> say, 1000 table entries for a pubid and only 1–2 of them are EXCEPT
> entries will not occur. Given this, the need for a composite index on
> (prpubid, prexcept) does not appear to be strongly justified to me.
> Please ignore my comment if you are already aware of this situation.
Thanks, I missed the fact that pg_publication_rel doesn't contain 
records for each table in the ALL-TABLES case. Case solved.

-- 
regards, Andrei Lepikhov,
pgEdge



pgsql-hackers by date:

Previous
From: Alexander Kukushkin
Date:
Subject: Re: synchronized_standby_slots behavior inconsistent with quorum-based synchronous replication
Next
From: Bernd Helmle
Date:
Subject: Re: Addition and subtraction operations for the interval and integer types