Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> "Jignesh K. Shah" <[EMAIL PROTECTED]> writes:
>>> New Lock Mode Proposed: LW_EX_OWNER (input on better name will be
>>> appreciated).
> We do something like this in the sinval code -- see SIGetDataEntry.
Yeah, that analogy occurred to me later --- EX_OWNER would be a close
match to what sinval is doing. However, adding a third mode to LWLocks
would certainly introduce extra cycles into what is already a hotspot,
and one use-case that is already working fine without it doesn't seem
like much of an argument. (ProcArray isn't a use-case because of the
commit interlock problem, and I didn't see any other proposed uses
that weren't mere hand-waving.)
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
