Re: relation OID in ReorderBufferToastReplace error message
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jeremy Schneider <schnjere@amazon.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2021-07-02T01:56:40Z
Lists: pgsql-hackers
Jeremy Schneider <schnjere@amazon.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
Commits
-
Back-patch "Add parent table name in an error in reorderbuffer.c."
- 4d3147070545 9.6.24 landed
- 13e52d7c5533 10.19 landed
- d61cdad0b524 11.14 landed
- 4048fc458175 12.9 landed
- 23469b867ac0 13.5 landed
- 9e84f6a72133 14.1 landed
-
Add parent table name in an error in reorderbuffer.c.
- 5e77625b260a 15.0 landed
-
Fix reorder buffer memory accounting for toast changes.
- df3640e5293d 15.0 cited
-
Add logical change details to logical replication worker errcontext.
- abc0910e2e0a 15.0 cited
-
Fix toast rewrites in logical decoding.
- 29b590547028 15.0 cited
-
Add error codes to some corruption log messages
- fd6ec93bf890 13.0 cited