| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: LWLockAcquire and LockBuffer mode argument |
| Date: | 2020-08-26 16:27:19 |
| Message-ID: | 20200826162719.GA10192@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-Aug-26, Robert Haas wrote:
> On Wed, Aug 26, 2020 at 7:47 AM Dagfinn Ilmari Mannsåker
> <ilmari(at)ilmari(dot)org> wrote:
> > Would it be possible to make the compat versions only available when
> > building extensions, but not to core code?
>
> I think that would be good if we can do it. We could even have it
> inside #ifdef LWLOCK_API_COMPAT, and extension authors who want the
> compatibility interface can define that.
We had ENABLE_LIST_COMPAT available for 16 years; see commits
d0b4399d81f3, 72b6ad631338, 1cff1b95ab6d. We could do the same here.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2020-08-26 17:17:10 | Re: [POC]Enable tuple change partition caused by BEFORE TRIGGER |
| Previous Message | Tom Lane | 2020-08-26 16:08:48 | Re: Compiler warning |