Re: Separating Buffer LWlocks

From: Andres Freund <andres(at)anarazel(dot)de>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Separating Buffer LWlocks
Date: 2015-09-08 18:19:08
Message-ID: 20150908181908.GH5084@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2015-09-08 14:15:32 -0400, Robert Haas wrote:
> We could do that, but I'm not sure just calling LWLockNewTrancheId()
> for all of the tranches would be so bad either.

To me that seems either fragile or annoying to use. If all backends call
LWLockNewTrancheId() we need to a be sure the callbacks are always going
to be called in the same order. Otherwise everyone needs to store the
tranche in shared memory (like xlog.c now does) which I find to be a
rather annoying requirement.

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2015-09-08 18:20:31 Re: Odd/undocumented precedence of concatenation operator
Previous Message Corey Huinker 2015-09-08 18:17:16 Re: proposal: function parse_ident