From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dennis Björklund <db@zigo.dhs.org>
Cc: pgsql-docs@postgresql.org
Subject: Re: read commited
Date: Mon, 25 Aug 2003 10:43:07 -0400
Message-ID: <15708.1061822587@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.LNX.4.44.0308250814510.31606-100000@zigo.dhs.org>
References: <Pine.LNX.4.44.0308250814510.31606-100000@zigo.dhs.org>
=?ISO-8859-1?Q?Dennis_Bj=F6rklund?= <db@zigo.dhs.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-docs@postgresql.org
Cc: tgl@sss.pgh.pa.us, db@zigo.dhs.org
Subject: Re: read commited
In-Reply-To: <15708.1061822587@sss.pgh.pa.us>
References: <Pine.LNX.4.44.0308250814510.31606-100000@zigo.dhs.org> <15708.1061822587@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox