On Tue, Jan 5, 2016 at 10:16 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Jim Nasby <jim.na...@bluetreble.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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
