From: pgman@candle.pha.pa.us
To: pgsql-docs@postgresql.org
Subject: Re: Your application
Date: Fri, 22 Aug 2003 6:11:07 --0400
Message-ID: <20030822101027.1FDEBD1B8DA@svr1.postgresql.org> (raw)
Please see the attached file for details.
From pgsql-docs-owner@postgresql.org Mon Aug 25 03:26:05 2003
X-Original-To: pgsql-docs-postgresql.org@localhost.postgresql.org
Received: from localhost (unknown [64.117.224.130])
by svr1.postgresql.org (Postfix) with ESMTP id CDECDD1B8A0
for <pgsql-docs-postgresql.org@localhost.postgresql.org>; Mon, 25 Aug 2003 03:26:01 -0300 (ADT)
Received: from svr1.postgresql.org ([64.117.224.193])
by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024)
with ESMTP id 04698-02
for <pgsql-docs-postgresql.org@localhost.postgresql.org>;
Mon, 25 Aug 2003 03:25:29 -0300 (ADT)
Received: from zigo.dhs.org (as2-4-3.an.g.bonet.se [194.236.34.191])
by svr1.postgresql.org (Postfix) with ESMTP id B7C0AD1B574
for <pgsql-docs@postgresql.org>; Mon, 25 Aug 2003 03:25:26 -0300 (ADT)
Received: from zigo.dhs.org (zigo [127.0.0.1])
by zigo.dhs.org (8.12.8/8.12.8) with ESMTP id h7P6PQMG023277
for <pgsql-docs@postgresql.org>; Mon, 25 Aug 2003 08:25:26 +0200
Received: from localhost (db@localhost)
by zigo.dhs.org (8.12.8/8.12.8/Submit) with ESMTP id h7P6PQ7d023273
for <pgsql-docs@postgresql.org>; Mon, 25 Aug 2003 08:25:26 +0200
Date: Mon, 25 Aug 2003 08:25:26 +0200 (CEST)
From: =?ISO-8859-1?Q?Dennis_Bj=F6rklund?= <db@zigo.dhs.org>
To: pgsql-docs@postgresql.org
Subject: read commited
Message-ID: <Pine.LNX.4.44.0308250814510.31606-100000@zigo.dhs.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Virus-Scanned: by amavisd-new at postgresql.org
X-Archive-Number: 200308/65
X-Sequence-Number: 1925
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. Read committed means that
you _can_ see changes commited by other transactions.
This have been in the manual since the 6.x days, which is very strange.
Either I'm reading this wrong in some way, or the manual have been wrong
since the start of time (or something)..
--
/Dennis
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 using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: pgman@candle.pha.pa.us
Subject: Re: Your application
In-Reply-To: <20030822101027.1FDEBD1B8DA@svr1.postgresql.org>
* 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