Re: relation OID in ReorderBufferToastReplace error message - Mailing list pgsql-hackers

From Schneider (AWS), Jeremy
Subject Re: relation OID in ReorderBufferToastReplace error message
Date
Msg-id 48B6BE63-FE39-45B8-9AD8-819DAAC5877F@amazon.com
Whole thread Raw
In response to Re: relation OID in ReorderBufferToastReplace error message  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: relation OID in ReorderBufferToastReplace error message  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> On Jul 1, 2021, at 18:57, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> 
> But I wonder why
> print the parent's OID, when we have access to its name.

Seems like a few people do schema-based multi-tenancy with similarly named relations in different namespaces, so I’d
havea preference for OID over an unqualified relation name. Also the error message shows the OID for the toast relation
sothis is consistent.
 

Relation name could work too though, especially if the schema was included

-Jeremy


Sent from my TI-83


pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Refactor "mutually exclusive options" error reporting code in parse_subscription_options
Next
From: Thomas Munro
Date:
Subject: Re: cutting down the TODO list thread