public inbox for [email protected]  

help / color / mirror / Atom feed

From: Oliver Crow <[email protected]>
To: [email protected]
To: [email protected]
Subject: Read Committed isolation
Date: Tue, 4 Mar 2003 12:58:25 -0800 (PST)
Message-ID: <[email protected]> (raw)


Hi all,

It seems to me that the PostgreSQL user's manual could be clearer on the
consequences of using the Read Committed isolation level.

It says "The partial transaction isolation provided by Read Committed
mode is adequate for many applications" ... "However, for applications
that do complex queries and updates, it may be necessary to guarantee a
more rigorously consistent view of the database".

It does not say what types of transactions will cause problems in Read
Committed mode, or what the consequences of those problems might be.
This is a point on which the manual ought to be explicit ... the potential
for intermittent creation of database inconsistencies is serious. For
example, if information from a select is passed via the application to an
update, the transaction could reintroduce stale information.

This message provides some good explanation with examples:
http://archives.postgresql.org/pgsql-hackers/2002-04/msg00150.php


It also speaks clearly about when a serializable transaction may need to
be repeated, and the possible trade off between using serializable or
SELECT FOR UPDATE.  Could an edited version of that message be included in
the manual?  (I'd be willing to assist with editing)


Thanks, Oliver

view thread (2+ messages)  latest in thread

reply

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: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: Read Committed isolation
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox