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=# Not sure how hard that would be to do within psql's current structure. regards, tom lane -- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers