On Tue, Feb 08, 2011 at 04:04:39PM -0600, Kevin Grittner wrote:
> (2) The predicate lock and lock target initialization code was
> initially copied and modified from the code for heavyweight locks.
> The heavyweight lock code adds 10% to the calculated maximum size.
> So I wound up doing that for PredicateLockTargetHash and
> PredicateLockHash, but didn't do it for SerializableXidHassh.
> Should I eliminate this from the first two, add it to the third, or
> leave it alone?
Actually, I think for SerializableXidHash we should probably just
initially allocate it at its maximum size. Then it'll match the
PredXact list which is allocated in full upfront, and there's no risk
of being able to allocate a transaction but not register its xid. In
fact, I believe there would be no way for starting a new serializable
transaction to fail.
Dan R. K. Ports MIT CSAIL http://drkp.net/
In response to
pgsql-hackers by date
|Next:||From: Jeff Davis||Date: 2011-02-09 00:58:09|
|Subject: Re: postponing some large patches to 9.2|
|Previous:||From: Tom Lane||Date: 2011-02-08 23:54:38|
|Subject: Re: Extensions versus pg_upgrade |