Re: FlexLocks

Kevin Grittner <kevin.grittner@wicourts.gov>

From: "Kevin Grittner" <Kevin.Grittner@wicourts.gov>

To: "Alvaro Herrera" <alvherre@commandprompt.com>, "Robert Haas" <robertmhaas@gmail.com>

Cc: "Simon Riggs" <simon@2ndquadrant.com>, "Pg Hackers" <pgsql-hackers@postgresql.org>

Date: 2011-11-15T20:47:54Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Fix copyright notices, other minor editing in new range-types code.
- f1585362856d 9.2.0 cited

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.

-Kevin