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
Date: Mon, 21 Oct 2024 12:06:27 -0400
Message-ID: <1568448.1729526787@sss.pgh.pa.us> (raw)
In-Reply-To: <18665-95be0e49a07d758c@postgresql.org>
References: <18665-95be0e49a07d758c@postgresql.org>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, nat@makarevitch.org, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18665: Breaking a foreign constraint: the error message may be more detailed
In-Reply-To: <1568448.1729526787@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox