Re: Add isCatalogRel in rmgrdesc - Mailing list pgsql-hackers

From Drouvot, Bertrand
Subject Re: Add isCatalogRel in rmgrdesc
Date
Msg-id 5429a088-c7bd-4c60-b300-01b069bc0540@gmail.com
Whole thread Raw
In response to Re: Add isCatalogRel in rmgrdesc  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
Hi,

On 12/12/23 10:15 AM, Michael Paquier wrote:
> On Tue, Dec 12, 2023 at 09:23:46AM +0100, Drouvot, Bertrand wrote:
>> Please find attached a patch to add this field in the related rmgrdesc (i.e
>> all the ones that already provide the snapshotConflictHorizon except the one
>> related to xl_heap_visible: indeed a new bit was added in its flag field in 6af1793954
>> instead of adding the isCatalogRel bool).
>>
>> I think it's worth it, as this new field could help diagnose conflicts issues (if any).
> 
> Agreed that this is helpful.

Thanks for looking at it!

>  One would likely guess if you are
> dealing with a catalog relation depending on its relfilenode, but that
> does not take into account user_catalog_table that can be set as a
> reloption, impacting the value of isCatalogRel stored in the records.

Exactly and not mentioning the other checks in RelationIsAccessibleInLogicalDecoding()
like the wal_level >= logical one.

Regards,

-- 
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Add isCatalogRel in rmgrdesc
Next
From: "Zhijie Hou (Fujitsu)"
Date:
Subject: RE: Synchronizing slots from primary to standby