It would probably also be worth monitoring the size of pg_locks to see
how many predicate locks are being held.

On Fri, Mar 18, 2011 at 12:50:16PM -0500, Kevin Grittner wrote:
> Even with the above information it may be far from clear where
> allocations are going past their maximum, since one HTAB could grab
> more than its share and starve another which is staying below its
> "maximum".  I'll take a look at the possibility of adding a warning
> or some such when an HTAB expands past its maximum size.

Yes -- considering how few shared memory HTABs have sizes that are
really dynamic, I'd be inclined to take a close look at SSI and
max_predicate_locks_per_transaction regardless of where the failed
allocation took place. But I am surprised to see that error message
without SSI's hint about increasing max_predicate_locks_per_xact.

Dan

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

In response to

• Re: SSI bug? at 2011-03-18 17:50:16 from Kevin Grittner

Responses

• Re: SSI bug? at 2011-03-18 20:51:11 from Kevin Grittner

pgsql-hackers by date

Next:	From: Alvaro Herrera	Date: 2011-03-18 18:55:14
	Subject: Re: Sync Rep and shutdown Re: Sync Rep v19
Previous:	From: Jim Nasby	Date: 2011-03-18 18:15:10
	Subject: Re: 2nd Level Buffer Cache