| From: | Kouber Saparev <kouber(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Postgres Bug <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: Unrecognized exception condition "deprecated_feature" |
| Date: | 2018-03-09 23:07:30 |
| Message-ID: | CAN4RuQvYau6gemXwR9o24+ZEeLx+bYjxR2p1S-tbLVTegjzwKw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
2018-03-10 0:44 GMT+02:00 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> 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.)
>
Indeed.
next unless $type eq 'E';
The only exception is 'string_data_right_truncation' (01004) because
actually it is duplicated further (22001).
Thanks for the clarification!
--
Kouber Saparev
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2018-03-10 00:17:48 | Re: Unrecognized exception condition "deprecated_feature" |
| Previous Message | Tom Lane | 2018-03-09 22:44:15 | Re: Unrecognized exception condition "deprecated_feature" |