Re: Add schema-qualified relnames in constraint error messages.

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: 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-02-11 17:50:00
Message-ID: CA+TgmoboJK14_NgUYeq=sXf_0xjcj2u62At3VmRvpJz4Sb=3fw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jan 5, 2016 at 10:16 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> writes:
>> FWIW, I suspect very few people know about the verbosity setting (I
>> didn't until a few months ago...) Maybe psql should hint about it the
>> first time an error is reported in a session.
>
> 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.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2016-02-11 17:50:58 Re: Performance degradation in commit ac1d794
Previous Message Tom Lane 2016-02-11 17:48:39 Re: Performance degradation in commit ac1d794