From: Tom Lane <tgl@sss.pgh.pa.us>
To: nat@makarevitch.org
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18665: Breaking a foreign constraint: the error message may
 be more detailed
In-reply-to: <18665-95be0e49a07d758c@postgresql.org>
References: <18665-95be0e49a07d758c@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Mon, 21 Oct 2024 01:51:22 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1568447.1729526787.1@sss.pgh.pa.us>
Date: Mon, 21 Oct 2024 12:06:27 -0400
Message-ID: <1568448.1729526787@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1568448.1729526787%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> A query breaking a foreign key triggers a "cannot truncate a table
> referenced in a foreign key constraint" error.  In the DETAIL section of
> this message the child table name isn't fully qualified: it omits its schema
> name.

By and large, we don't include objects' schema names in error messages
ever.  I'm not sure why this specific one should break that habit.

If you want to (re)start a conversation about whether more error
messages should include schema names, you can ... but a bug report
is not the mechanism for doing that.  This is not a bug, it's
acting as designed and in keeping with a lot of other code.

			regards, tom lane