Re: LWLockAcquire and LockBuffer mode argument

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: LWLockAcquire and LockBuffer mode argument
Date: 2020-08-25 18:22:28
Message-ID: CA+TgmoZSgLgYx-NJOf1j--h_EoS+tSSQSaaB2iv_6Hf8ZDT4cA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Aug 25, 2020 at 2:17 PM Andres Freund <andres(at)anarazel(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2020-08-25 18:30:02 Re: LWLockAcquire and LockBuffer mode argument
Previous Message Robert Haas 2020-08-25 18:21:23 Re: recovering from "found xmin ... from before relfrozenxid ..."