From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Kouber Saparev <kouber(at)gmail(dot)com>, Postgres Bug <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: Unrecognized exception condition "deprecated_feature" |
Date: | 2018-03-10 02:19:25 |
Message-ID: | 20180310021925.hoegs5fh2s4huiv4@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 2018-03-10 02:12:39 +0000, Andrew Gierth wrote:
> >>>>> "Tom" == Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2018-03-10 02:24:18 | Re: Unrecognized exception condition "deprecated_feature" |
Previous Message | Andrew Gierth | 2018-03-10 02:12:39 | Re: Unrecognized exception condition "deprecated_feature" |