On Tue, Jul 27, 2004 at 01:32:01PM -0400, Tom Lane wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > There are some likely controversial changes; the Xid caches, in the
> > first place.
> No kidding ;-)
> Do you have any theoretical or practical evidence for the usefulness of
> the negxids cache? Seems to me the shared memory space would be better
> spent on allowing deeper nesting of the running-subxids list. Also,
> what happened to marking whether the running-subxids list has
> overflowed? If none of them have then there's no need to wonder whether
> we have a still-running subxact.
Oh, sure, I had forgot about the overflow flag. I am working on that
> The apparent lack of any locking on these data structures seems wrong
Well, storing the main Xid of a transaction in PGPROC is regarded as
"atomic" and it has no locking (other than SInvalLock in shared mode).
I think the correct solution would be to lock both the main Xid and the
XidCache with a per-backend LWLock, but you already rejected that idea.
My current patch uses SInvalLock in shared mode to protect reading and
writing the XidCaches. I am not sure this is a very good idea, but it
doesn't seem unreasonable either.
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
"Et put se mouve" (Galileo Galilei)
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])