| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | "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 00:42:26 |
| Message-ID: | 30525.1520642546@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Andres Freund <andres(at)anarazel(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2018-03-10 00:55:37 | Re: Unrecognized exception condition "deprecated_feature" |
| Previous Message | Andres Freund | 2018-03-10 00:17:48 | Re: Unrecognized exception condition "deprecated_feature" |