| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, "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-29 01:22:42 |
| Message-ID: | 1920.1522286562@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> writes:
>>> 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.
> Something like this? Or I guess src/backend/Makefile could do it directly.
Patch seems reasonable as far as it goes, but what about the MSVC
infrastructure?
Also, do we need to discuss exactly where it's being installed to?
Is the choice made here easy for an extension Makefile to locate?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2018-03-29 01:46:47 | Re: Unrecognized exception condition "deprecated_feature" |
| Previous Message | Thomas Munro | 2018-03-29 00:41:00 | Re: Unrecognized exception condition "deprecated_feature" |