Re: Replace is_publishable_class() with relispublishable column in pg_class

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 09:13:42
Message-ID: CAA4eK1KE=tNHcN3Qp0FZVwDnt4rF2zwHy8NgAdG3oPqixdzOsA@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...
>
> 0. AFAIK, anything named with a "pg_" prefix generally means that the
> named thing is intended for PG internal use, right?
>
> 1. So, the CLT should be automatically named to have a "pg_" prefix,
> indicating that it really is an internal table, albeit not a system
> catalog. IIRC, this kind of name was a recent suggestion anyhow.
>

We would also like to give user a provision to provide
conflict_table|conflict_log name. In general also, I am not sure if
assuming this is a good idea as there could be some other internal
table if not now then in future where we would like to allow
replication by default.

--
With Regards,
Amit Kapila.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bertrand Drouvot 2025-12-17 09:24:31 Re: Fix and improve allocation formulas
Previous Message Heikki Linnakangas 2025-12-17 09:06:36 Re: Serverside SNI support in libpq