From: | Peter Geoghegan <pg(at)heroku(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Petr Korobeinikov <pkorobeinikov(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Add schema-qualified relnames in constraint error messages. |
Date: | 2016-04-02 23:53:22 |
Message-ID: | CAM3SWZSfm1EUdf7a0vNR=SAumit0FzqaA32TkKn97+HqqNskVw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Feb 11, 2016 at 9:50 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> Actually, what'd be really handy IMO is something to regurgitate the
>> most recent error in verbose mode, without making a permanent session
>> state change. Something like
>>
>> regression=# insert into bar values(1);
>> ERROR: insert or update on table "bar" violates foreign key constraint "bar_f1_fkey"
>> DETAIL: Key (f1)=(1) is not present in table "foo".
>> regression=# \saywhat
>> ERROR: 23503: insert or update on table "bar" violates foreign key constraint "bar_f1_fkey"
>> DETAIL: Key (f1)=(1) is not present in table "foo".
>> SCHEMA NAME: public
>> TABLE NAME: bar
>> CONSTRAINT NAME: bar_f1_fkey
>> LOCATION: ri_ReportViolation, ri_triggers.c:3326
>> regression=#
>
> Wow, that's a fabulous idea. I see Oleksandr has tried to implement
> it, although I haven't looked at the patch. But I think this would be
> REALLY helpful.
+1
--
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | Alex Shulgin | 2016-04-03 01:43:47 | Re: More stable query plans via more predictable column statistics |
Previous Message | Peter Geoghegan | 2016-04-02 23:50:08 | Re: Using quicksort for every external sort run |