Re: FlexLocks - Mailing list pgsql-hackers

From Robert Haas
Subject Re: FlexLocks
Date
Msg-id CA+TgmoYjBS3xotBuZ+GTxfTpnNLT7c2Gyx6=vS9xN11BxEdvZw@mail.gmail.com
Whole thread Raw
In response to Re: FlexLocks  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-hackers
On Tue, Nov 15, 2011 at 3:47 PM, Kevin Grittner
<Kevin.Grittner@wicourts.gov> wrote:
> Alvaro Herrera <alvherre@commandprompt.com> wrote:
>
>> As Kevin says nearby it's likely that we could find some way to
>> rewrite the SLRU (clog and such) locking protocol using these new
>> things too.
>
> Yeah, I really meant all SLRU, not just clog.  And having seen what
> Robert has done here, I'm kinda glad I haven't gotten around to
> trying to reduce LW lock contention yet, even though we're getting
> dangerously far into the release cycle -- I think it can be done
> much better with the, er, flexibility offered by the FlexLock patch.

I've had a thought that the SLRU machinery could benefit from having
the concept of a "pin", which it currently doesn't.  I'm not certain
whether that thought is correct.

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


pgsql-hackers by date:

Previous
From: Royce Ausburn
Date:
Subject: Re: [PATCH] Unremovable tuple monitoring
Next
From: "Andrew Dunstan"
Date:
Subject: Re: pg_restore --no-post-data and --post-data-only