Re: Unrecognized exception condition "deprecated_feature" - Mailing list pgsql-bugs

From Andres Freund
Subject Re: Unrecognized exception condition "deprecated_feature"
Date
Msg-id 20180310021925.hoegs5fh2s4huiv4@alap3.anarazel.de
Whole thread Raw
In response to Re: Unrecognized exception condition "deprecated_feature"  (Andrew Gierth <andrew@tao11.riddles.org.uk>)
Responses Re: Unrecognized exception condition "deprecated_feature"  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-bugs
On 2018-03-10 02:12:39 +0000, Andrew Gierth wrote:
> >>>>> "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.

Seems entirely reasonable to install it from my POV.

Greetings,

Andres Freund


pgsql-bugs by date:

Previous
From: Andrew Gierth
Date:
Subject: Re: Unrecognized exception condition "deprecated_feature"
Next
From: Alvaro Herrera
Date:
Subject: Re: Unrecognized exception condition "deprecated_feature"