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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Kirill Reshke <reshkekirill(at)gmail(dot)com>
Cc: keeshd(at)keeshinds(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19352: SQL Error messages do not include schema name along with table or data object name.
Date: 2025-12-12 15:39:55
Message-ID: 994716.1765553995@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Kirill Reshke <reshkekirill(at)gmail(dot)com> writes:
> On Fri, 12 Dec 2025 at 13:33, PG Bug reporting form
> <noreply(at)postgresql(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2025-12-12 16:54:44 Re: BUG #19353: Error XX000 if referencing expanded array in grouping set: variable not found in subplan target list
Previous Message Tom Lane 2025-12-12 15:26:12 Re: Bug in sub-query