Re: User-facing aspects of serializable transactions - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: User-facing aspects of serializable transactions
Date
Msg-id 200905281543.26223.peter_e@gmx.net
Whole thread Raw
In response to Re: User-facing aspects of serializable transactions  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: User-facing aspects of serializable transactions  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Thursday 28 May 2009 15:24:59 Heikki Linnakangas wrote:
> I don't think you need that for predicate locking. To determine if e.g
> an INSERT and a SELECT conflict, you need to determine if the INSERTed
> tuple matches the predicate in the SELECT. No need to deduce anything
> between two predicates, but between a tuple and a predicate.

That might the easy part.  The hard part is determining whether a SELECT and 
an UPDATE conflict.


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: User-facing aspects of serializable transactions
Next
From: Michael Meskes
Date:
Subject: Re: Compiler warning cleanup - unitilized const variables, pointer type mismatch