Re: [proposal] Add an option for returning SQLSTATE in psql error message
didier <did447@gmail.com>
From: didier <did447@gmail.com>
To: andrew@tao11.riddles.org.uk
Cc: Tom Lane <tgl@sss.pgh.pa.us>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2018-12-03T15:40:54Z
Lists: pgsql-hackers
Attachments
- master_psql_error_output.diff (text/x-patch) patch
Attached a POC adding a new variable ECHO_ERROR \set ECHO_ERROR text|none|psqlstate On Mon, Dec 3, 2018 at 2:47 AM Andrew Gierth <andrew@tao11.riddles.org.uk> wrote: > > >>>>> "Tom" == Tom Lane <tgl@sss.pgh.pa.us> writes: > > Tom> I don't buy that argument. We use psql's normal display in all the > Tom> regular regression tests, and it's not a big maintenance problem. > > The regular regression tests have the advantage that they don't need to > work across pg versions. > > It is more of a problem for extensions; I just ran into this myself in > fact, with a test failing because "invalid input syntax for integer" got > changed to "invalid input syntax for type integer". > > -- > Andrew (irc:RhodiumToad)
Commits
-
Add a "SQLSTATE-only" error verbosity option to libpq and psql.
- 7bac3acab4d5 12.0 landed