Horton

Re: Replace is_publishable_class() with relispublishable column in pg_class

Amit Kapila <amit.kapila16@gmail.com>

View thread
From: Amit Kapila <amit.kapila16@gmail.com>
To: Peter Smith <smithpb2250@gmail.com>
Cc: Andres Freund <andres@anarazel.de>, Dilip Kumar <dilipbalaut@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-12-17T12:23:56Z
Lists: pgsql-hackers 
On Wed, Dec 17, 2025 at 12:37 PM Peter Smith <smithpb2250@gmail.com> wrote:
>
> Here is a completely different idea. This may solve the immediate
> problem re the replication of the Conflict Log Table (CLT) at least...
>

Another idea could be that at the startup (pgoutput_startup), we can
form a conflict_table cache and then use it to determine whether to
send the change or not? Along with that we need to consider whether
publication explicitly indicates that a conflict_table changes needs
to be replicated or not.

-- 
With Regards,
Amit Kapila.