Re: BUG #18665: Breaking a foreign constraint: the error message may be more detailed - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #18665: Breaking a foreign constraint: the error message may be more detailed
Date
Msg-id 1568448.1729526787@sss.pgh.pa.us
Whole thread Raw
In response to BUG #18665: Breaking a foreign constraint: the error message may be more detailed  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
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



pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #18668: [Windows] September 2024 releases (17.0, 16.4, etc) all include older libiconv-2.dll
Next
From: Alex Richman
Date:
Subject: Re: Logical Replica ReorderBuffer Size Accounting Issues