| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Petr Korobeinikov <pkorobeinikov(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add schema-qualified relnames in constraint error messages. |
| Date: | 2016-01-06 02:36:49 |
| Message-ID: | 568C7DC1.9060405@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1/5/16 7:21 PM, Tom Lane wrote:
> What seems more likely to be useful and to not break anything is to push
> forward on adding PG_DIAG_SCHEMA_NAME and similar auxiliary fields to more
> error messages (see errtable() and siblings). That would allow
> applications to extract this information automatically and reliably.
> Only after that work is complete and there's been a reasonable amount of
> time for clients to start relying on it can we really start thinking about
> whacking the message texts around.
+1, but...
does psql do anything with those fields? ISTM the biggest use for this
info is someone sitting at psql or pgAdmin.
Maybe schema info could be presented in HINT or DETAIL messages as well?
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-01-06 02:41:36 | Re: Add schema-qualified relnames in constraint error messages. |
| Previous Message | Alvaro Herrera | 2016-01-06 02:35:54 | Re: No Issue Tracker - Say it Ain't So! |