Re: LWLockAcquire and LockBuffer mode argument - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: LWLockAcquire and LockBuffer mode argument
Date
Msg-id 20200826162719.GA10192@alvherre.pgsql
Whole thread Raw
In response to Re: LWLockAcquire and LockBuffer mode argument  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On 2020-Aug-26, Robert Haas wrote:

> On Wed, Aug 26, 2020 at 7:47 AM Dagfinn Ilmari Mannsåker
> <ilmari@ilmari.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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Compiler warning
Next
From: Alvaro Herrera
Date:
Subject: Re: [POC]Enable tuple change partition caused by BEFORE TRIGGER