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

Re: User-facing aspects of serializable transactions

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Greg Stark" <stark(at)enterprisedb(dot)com>
Cc: "Heikki Linnakangas" <heikki(dot)linnakangas(at)enterprisedb(dot)com>, "Jeff Davis" <pgsql(at)j-davis(dot)com>, "<pgsql-hackers(at)postgresql(dot)org>" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: User-facing aspects of serializable transactions
Date: 2009-05-28 15:37:30
Message-ID: 4A1E6969.EE98.0025.1@wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-hackers
Greg Stark <stark(at)enterprisedb(dot)com> wrote:
 
> I would want any serialization failure to be
> justifiable by simple inspection of the two transactions.
 
BTW, there are often three (or more) transaction involved in creating
a serialization failure, where any two of them alone would not fail. 
You probably knew that, but just making sure....
 
-Kevin

In response to

Responses

pgsql-hackers by date

Next:From: Robert HaasDate: 2009-05-28 15:38:07
Subject: Re: PostgreSQL Developer meeting minutes up
Previous:From: Simon RiggsDate: 2009-05-28 15:36:10
Subject: Re: Clean shutdown and warm standby

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