Re: SSI patch version 14 - Mailing list pgsql-hackers

From Dan Ports
Subject Re: SSI patch version 14
Date
Msg-id 20110208205305.GY9421@csail.mit.edu
Whole thread Raw
In response to Re: SSI patch version 14  (Dan Ports <drkp@csail.mit.edu>)
List pgsql-hackers
One other nit re. the predicate lock table size GUCs: the out-of-memory
case in RegisterPredicateLockingXid (predicate.c:1592 in my tree) gives
the hint to increase max_predicate_locks_per_transaction. I don't think
that's correct, since that GUC isn't used to size SerializableXidHash.

In fact, that error shouldn't arise at all because if there was room in
PredXact to register the transaction, then there should be room to
register it's xid in SerializableXidHash. Except that it's possible for
something else to allocate all of our shared memory and thus prevent
SerializbleXidHash from reaching its intended max capacity.

In general, it might be worth considering making a HTAB's max_size a
hard limit, but that's a larger issue. Here, it's probably worth just
removing the hint.

Dan

-- 
Dan R. K. Ports              MIT CSAIL                http://drkp.net/


pgsql-hackers by date:

Previous
From: Dimitri Fontaine
Date:
Subject: Re: Extensions versus pg_upgrade
Next
From: Dimitri Fontaine
Date:
Subject: Re: Extensions versus pg_upgrade