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 200905281520.13620.peter_e@gmx.net
Whole thread Raw
In response to Re: User-facing aspects of serializable transactions  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: User-facing aspects of serializable transactions  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
On Thursday 28 May 2009 04:49:19 Tom Lane wrote:
> Yeah.  The fundamental problem with all the "practical" approaches I've
> heard of is that they only work for a subset of possible predicates
> (possible WHERE clauses).  The idea that you get true serializability
> only if your queries are phrased just so is ... icky.  So icky that
> it doesn't sound like an improvement over what we have.

Is it even possible to have a predicate locking implementation that can verify 
whether an arbitrary predicate implies another arbitrary predicate?  And this 
isn't constraint exclusion, where it is acceptable to have false negatives.


pgsql-hackers by date:

Previous
From: Zdenek Kotala
Date:
Subject: Re: Compiler warning cleanup - unitilized const variables, pointer type mismatch
Next
From: Stephen Frost
Date:
Subject: Re: search_path vs extensions