From: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: duplicate function oid symbols |
Date: | 2020-10-28 19:58:33 |
Message-ID: | CAFBsxsHxBB+VE91XmTGLz3O6cwWYkh10VEyFeD4dUH6LrXZZtQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Oct 28, 2020 at 3:24 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Nah. What I'm imagining is just that pg_type.h contains
>
> #ifdef EXPOSE_TO_CLIENT_CODE
>
> /*
> * Backwards compatibility for ancient random spellings of OID macros.
> * Don't use these macros in new code.
> */
> #define CASHOID MONEYOID
> #define LSNOID PG_LSNOID
>
> #endif
>
Here is a quick patch implementing this much.
--
John Naylor
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Attachment | Content-Type | Size |
---|---|---|
forbid-custom-pg-type-symbols.patch | application/octet-stream | 12.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2020-10-28 19:59:01 | Re: Deduplicate aggregates and transition functions in planner |
Previous Message | Alvaro Herrera | 2020-10-28 19:58:10 | Re: libpq compression |