Re: Unrecognized exception condition "deprecated_feature"
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: "David G. Johnston" <david.g.johnston@gmail.com>,
Kouber Saparev <kouber@gmail.com>,
Postgres Bug <pgsql-bugs@postgresql.org>
Date: 2018-03-10T00:42:26Z
Lists: pgsql-bugs
Andres Freund <andres@anarazel.de> writes: > On 2018-03-09 17:44:15 -0500, Tom Lane wrote: >> I'm not entirely sure why we have this errcode at all, as it doesn't >> seem to be used anywhere. > It used to be used till: > ... > While it wasn't used for ~12 years, it seems like a useful > concept. OTOH, we've tried hard to avoid warnings like that due to the > log spam... Yeah, I'm not that excited about removing it. Probably a more useful thing to debate is whether we ought to change the policy about omitting warning conditions from plpgsql's conversion list. While the core code hasn't got a use for that (since we never actually throw errors with such SQLSTATEs), this complaint seems to indicate that users would like to use them in RAISE. (I'd still skip "success" conditions, like 00000, in any case.) regards, tom lane
Commits
-
Install errcodes.txt for use by extensions.
- 1fd869066863 11.0 landed
-
Adjust input routines for float4, float8 and oid to reject the empty string
- 975e27377aad 8.1.0 cited
-
Emit a warning when an empty string is input to the oid, float4, and
- 2146bfc869bf 8.0.0 cited