Re: BUFFER_LOCK_* synonyms

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: BUFFER_LOCK_* synonyms
Date: 2015-09-16 16:45:40
Message-ID: CAM3SWZQD_1vv1Ds+=LeRpKRGYS4pPA7wHV-Atsm5BosyqtYizg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Sep 16, 2015 at 9:30 AM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> I was annoyed by this more than once too. It also bugs me that unlocking
> a buffer is spelled LockBuffer(..., BUFFER_LOCK_UNLOCK) - that just
> reads wrong.

Pretty sure that this was discussed a couple of times before. I find
it annoying myself, but I tend to doubt that it's worth changing.

--
Peter Geoghegan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Korotkov 2015-09-16 16:47:41 Re: Use pg_rewind when target timeline was switched
Previous Message Jesper Pedersen 2015-09-16 16:44:21 Re: Additional LWLOCK_STATS statistics