Re: [proposal] Add an option for returning SQLSTATE in psql error message - Mailing list pgsql-hackers

From Andrew Gierth
Subject Re: [proposal] Add an option for returning SQLSTATE in psql error message
Date
Msg-id 87k1kr4c6v.fsf@news-spur.riddles.org.uk
Whole thread Raw
In response to Re: [proposal] Add an option for returning SQLSTATE in psql error message  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [proposal] Add an option for returning SQLSTATE in psql error message  (didier <did447@gmail.com>)
List pgsql-hackers
>>>>> "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)


pgsql-hackers by date:

Previous
From: "Ideriha, Takeshi"
Date:
Subject: RE: idle-in-transaction timeout error does not give a hint
Next
From: Andrew Gierth
Date:
Subject: Re: AllocSetContextCreate changes breake extensions