Horton

Re: Unrecognized exception condition "deprecated_feature"

Andrew Gierth <andrew@tao11.riddles.org.uk>

View thread View on postgr.es
From: Andrew Gierth <andrew@tao11.riddles.org.uk>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andres Freund <andres@anarazel.de>, "David G. Johnston" <david.g.johnston@gmail.com>, Kouber Saparev <kouber@gmail.com>, Postgres Bug <pgsql-bugs@postgresql.org>
Date: 2018-03-10T02:12:39Z
Lists: pgsql-bugs 
>>>>> "Tom" == Tom Lane <tgl@sss.pgh.pa.us> writes:

 Tom> Yeah, I'm not that excited about removing it. Probably a more
 Tom> useful thing to debate is whether we ought to change the policy
 Tom> about omitting warning conditions from plpgsql's conversion list.
 Tom> While the core code hasn't got a use for that (since we never
 Tom> actually throw errors with such SQLSTATEs), this complaint seems
 Tom> to indicate that users would like to use them in RAISE.

While we're on the topic, I know of at least one other author of a
non-core PL (besides myself) that has been frustrated by the fact that
errcodes.txt is not installed anywhere, making it impossible to
autogenerate a plerrcodes.h file in the extension build process.

-- 
Andrew (irc:RhodiumToad)

Commits

  1. Install errcodes.txt for use by extensions.

  2. Adjust input routines for float4, float8 and oid to reject the empty string

  3. Emit a warning when an empty string is input to the oid, float4, and