Re: relation OID in ReorderBufferToastReplace error message

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jeremy Schneider <schnjere(at)amazon(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: relation OID in ReorderBufferToastReplace error message
Date: 2021-07-02 01:56:40
Message-ID: 772142.1625191000@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jeremy Schneider <schnjere(at)amazon(dot)com> writes:
> Nonetheless, in the process of troubleshooting it occurred to me that
> this error message would be more useful in general if it included the
> base relation OID in the error message. Amit suggested a separate thread
> - so here we are.  :)
> Anyone have thoughts?  Would I need a commitfest entry to propose a
> two-line tweak like this?

Probably not, unless it slips through the cracks. But I wonder why
print the parent's OID, when we have access to its name.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2021-07-02 02:05:08 Re: Allow batched insert during cross-partition updates
Previous Message Michael Paquier 2021-07-02 01:53:07 Re: Mention --enable-tap-tests in the TAP section page