Re: SSI memory mitigation & false positive degradation - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: SSI memory mitigation & false positive degradation
Date
Msg-id 4D1B23EC0200002500038D80@gw.wicourts.gov
Whole thread Raw
In response to Re: SSI memory mitigation & false positive degradation  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: SSI memory mitigation & false positive degradation  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-hackers
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> wrote:
> Looking at the predicate lock splitting, it occurs to me that
> it's possible for a non-serializable transaction to be canceled if
> it needs to split a predicate lock held by a concurrent
> serializable transaction, and you run out of space in the shared
> memory predicate lock area.
Good point.  We don't want that, for sure.
> Any chance of upgrading the lock to a relation lock, or killing
> the serializable transaction instead?
Absolutely.  Good suggestion.  Thanks!
-Kevin


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg_streamrecv for 9.1?
Next
From: Robert Haas
Date:
Subject: Re: and it's not a bunny rabbit, either