| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
| Cc: | 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-16 16:28:11 |
| Message-ID: | lyjqewaftw3gjpkkfhm6ldjsafgmrf3g3ossqobrsfg2bjdkja@rukmok5tbjfg |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2025-12-16 21:19:21 +0530, Dilip Kumar wrote:
> Motivation
> ========
> 1) The check is performed frequently in the logical decoding path
> (e.g., in pgoutput_change and pgoutput_truncate). Moving this to a
> cached catalog attribute in pg_class allows for a simple check.
You could solve this more resource-efficiently by putting the information in
the relcache entry.
> 2) As suggested by Amit Kpila [2], for the upcoming Conflict Log Table
> feature, we need a clean way to exclude these internal conflict log
> tables from publication. A catalog flag allows us to set this property
> at relation creation rather than adding more special cases.
Seems like the issue here also could be addressed the same way?
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Srinath Reddy Sadipiralla | 2025-12-16 16:39:12 | Re: Adding vacuum test case of setting the VM when heap page is unmodified |
| Previous Message | Melanie Plageman | 2025-12-16 16:07:17 | Re: eliminate xl_heap_visible to reduce WAL (and eventually set VM on-access) |