| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Peter Smith <smithpb2250(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Replace is_publishable_class() with relispublishable column in pg_class |
| Date: | 2025-12-17 12:23:56 |
| Message-ID: | CAA4eK1JrwW4Er6aEUMM5y-8kuECsXT3ye_vn6rC8ye9RMcHb2A@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Dec 17, 2025 at 12:37 PM Peter Smith <smithpb2250(at)gmail(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zsolt Parragi | 2025-12-17 13:15:30 | Re: Make PGOAUTHCAFILE in libpq-oauth work out of debug mode |
| Previous Message | Amit Kapila | 2025-12-17 12:04:15 | Re: DOCS - Clarify the publication 'publish_via_partition_root' default value. |