Request a Demo
Home   >   mailing lists

Re: Replace is_publishable_class() with relispublishable column in pg_class - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Replace is_publishable_class() with relispublishable column in pg_class
Date
Msg-id CAA4eK1JrwW4Er6aEUMM5y-8kuECsXT3ye_vn6rC8ye9RMcHb2A@mail.gmail.com
Whole thread Raw
In response to Re: Replace is_publishable_class() with relispublishable column in pg_class  (Peter Smith <smithpb2250@gmail.com>)
List pgsql-hackers
Tree view 
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.

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: DOCS - Clarify the publication 'publish_via_partition_root' default value.
Next
From: Zsolt Parragi
Date:
Subject: Re: Make PGOAUTHCAFILE in libpq-oauth work out of debug mode