Skip site navigation (1) Skip section navigation (2)

Re: SSI memory mitigation & false positive degradation

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Heikki Linnakangas" <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: <drkp(at)csail(dot)mit(dot)edu>,<pgsql-hackers(at)postgresql(dot)org>
Subject: Re: SSI memory mitigation & false positive degradation
Date: 2010-12-29 18:05:00
Message-ID: 4D1B23EC0200002500038D80@gw.wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-hackers
Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)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

In response to

Responses

pgsql-hackers by date

Next:From: Robert HaasDate: 2010-12-29 18:35:07
Subject: Re: and it's not a bunny rabbit, either
Previous:From: Tom LaneDate: 2010-12-29 18:01:54
Subject: Re: pg_streamrecv for 9.1?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group