From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | 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-09 22:44:15 |
Message-ID: | 24803.1520635455@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> On Fri, Mar 9, 2018 at 11:55 AM, Kouber Saparev <kouber(at)gmail(dot)com> wrote:
>> For some reason using an error code of 'deprecated_feature' does not work,
>> while its equivalent '01P01' works just fine.
> While I haven't looked at the source code or docs for this I'm wondering
> why you believe this is a bug in the first place.
This isn't specific to ERRCODE_WARNING_DEPRECATED_FEATURE; if you look
at generate-plerrcodes.pl you'll see it only collects error codes, not
warning codes, for use in plpgsql's mapping table. It's documented, too:
Appendix A says
(Note that PL/pgSQL does not recognize warning, as opposed to error,
condition names; those are classes 00, 01, and 02.)
I'm not entirely sure why we have this errcode at all, as it doesn't
seem to be used anywhere.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Kouber Saparev | 2018-03-09 23:07:30 | Re: Unrecognized exception condition "deprecated_feature" |
Previous Message | Jeff Janes | 2018-03-09 22:36:22 | Re: Build or update inarray GIST index very slow. |