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

Re: read commited

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Dennis Björklund <db(at)zigo(dot)dhs(dot)org>
Cc: pgsql-docs(at)postgresql(dot)org
Subject: Re: read commited
Date: 2003-08-25 14:43:07
Message-ID: 15708.1061822587@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-docs
=?ISO-8859-1?Q?Dennis_Bj=F6rklund?= <db(at)zigo(dot)dhs(dot)org> writes:
> The first part in the doc about concurrency with Read Commited 
> transactions (12.2.1 in devel doc) it says:
> | Read Committed is the default isolation level in PostgreSQL.
> | When a transaction runs on this isolation level, a SELECT query
> | sees only data committed before the query began; it never sees
> | either uncommitted data or changes committed during query
> | execution by concurrent transactions. 

> And that describes serializable transactions.

No, it doesn't.  The critical phrase here is "data committed before the
*query* began" ... not "data committed before the *transaction* began".

			regards, tom lane

Responses

pgsql-docs by date

Next:From: Dennis BjörklundDate: 2003-08-25 15:27:30
Subject: Re: read commited
Previous:From: Sumaira Maqsood AliDate: 2003-08-24 22:28:45
Subject: LOCK.tag(figuring out granularity of lock)

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