| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | nat(at)makarevitch(dot)org |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #18665: Breaking a foreign constraint: the error message may be more detailed |
| Date: | 2024-10-21 16:06:27 |
| Message-ID: | 1568448.1729526787@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
PG Bug reporting form <noreply(at)postgresql(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex Richman | 2024-10-21 16:32:57 | Re: Logical Replica ReorderBuffer Size Accounting Issues |
| Previous Message | PG Bug reporting form | 2024-10-21 15:49:16 | BUG #18668: [Windows] September 2024 releases (17.0, 16.4, etc) all include older libiconv-2.dll |