Re: BUG #19352: SQL Error messages do not include schema name along with table or data object name. - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #19352: SQL Error messages do not include schema name along with table or data object name.
Date
Msg-id 994716.1765553995@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #19352: SQL Error messages do not include schema name along with table or data object name.  (Kirill Reshke <reshkekirill@gmail.com>)
List pgsql-bugs
Kirill Reshke <reshkekirill@gmail.com> writes:
> On Fri, 12 Dec 2025 at 13:33, PG Bug reporting form
> <noreply@postgresql.org> wrote:
>> Ideally this error message would be clearer if the schema name was included
>> with the data table or object name.

> So, if we do anything about this, we need to change all of these
> places... This is a big amount of work and would be HEAD-only.

Yeah, at a guess we'd be talking about touching a couple of thousand
places if we were to apply such a policy uniformly.  This has been
debated in the past and the answer has always come out "no"; not
just because of the work, but because it'd make errors more verbose
but frequently not more helpful.

As Álvaro notes nearby, we do have provisions for reporting associated
schema names as secondary error fields, although I think that's only
been implemented in a few dozen places.

            regards, tom lane



pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Bug in sub-query
Next
From: Tom Lane
Date:
Subject: Re: BUG #19353: Error XX000 if referencing expanded array in grouping set: variable not found in subplan target list