On Wed, 2009-12-02 at 12:49 +0200, Heikki Linnakangas wrote:
> If a read-only transaction holds a lot of locks, consuming so much
> lock space that there's none left for the startup process to hold the
> lock it wants, it will abort and bring down postmaster. The patch
> attempts to kill any conflicting lockers, but those are handled fine
> already (if there's any conflicting locks, LockAcquire will return
> LOCKACQUIRE_NOT_AVAIL anyway). The problem is with non-conflicting
> locks using up the lock space.
Oh dear, another "nuke 'em all from orbit" scenario. Will do.
-- Simon Riggs www.2ndQuadrant.com