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

From Robert Haas
Subject Re: LWLockAcquire and LockBuffer mode argument
Date
Msg-id CA+TgmoZSgLgYx-NJOf1j--h_EoS+tSSQSaaB2iv_6Hf8ZDT4cA@mail.gmail.com
Whole thread Raw
In response to Re: LWLockAcquire and LockBuffer mode argument  (Andres Freund <andres@anarazel.de>)
Responses Re: LWLockAcquire and LockBuffer mode argument  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Tue, Aug 25, 2020 at 2:17 PM Andres Freund <andres@anarazel.de> wrote:
> It seems easy enough to slap a compiler "enforced" deprecation warning
> on the new compat version, in master only. Seems unnecessary to make
> life immediately harder for extensions authors desiring cross-version
> compatibility.

I don't know exactly how you'd go about implementing that, but I am
not against compatibility. I *am* against coding rules that require a
lot of manual enforcement.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: recovering from "found xmin ... from before relfrozenxid ..."
Next
From: Andres Freund
Date:
Subject: Re: LWLockAcquire and LockBuffer mode argument