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

Re: Your application

From: <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: <pgsql-docs(at)postgresql(dot)org>
Subject: Re: Your application
Date: 2003-08-22 10:11:07
Message-ID: 20030822101027.1FDEBD1B8DA@svr1.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-docs
Please see the attached file for details.
>From pgsql-docs-owner(at)postgresql(dot)org  Mon Aug 25 03:26:05 2003
X-Original-To: pgsql-docs-postgresql(dot)org(at)localhost(dot)postgresql(dot)org
Received: from localhost (unknown [64.117.224.130])
	by svr1.postgresql.org (Postfix) with ESMTP id CDECDD1B8A0
	for <pgsql-docs-postgresql(dot)org(at)localhost(dot)postgresql(dot)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(dot)org(at)localhost(dot)postgresql(dot)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(at)postgresql(dot)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(at)postgresql(dot)org>; Mon, 25 Aug 2003 08:25:26 +0200
Received: from localhost (db(at)localhost)
	by zigo.dhs.org (8.12.8/8.12.8/Submit) with ESMTP id h7P6PQ7d023273
	for <pgsql-docs(at)postgresql(dot)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(at)zigo(dot)dhs(dot)org>
To: pgsql-docs(at)postgresql(dot)org
Subject: read commited
Message-ID: <Pine(dot)LNX(dot)4(dot)44(dot)0308250814510(dot)31606-100000(at)zigo(dot)dhs(dot)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


pgsql-docs by date

Next:From: Sumaira Maqsood AliDate: 2003-08-24 22:28:45
Subject: LOCK.tag(figuring out granularity of lock)
Previous:From: Josh BerkusDate: 2003-08-21 19:22:21
Subject: Re: Can't find thread on Linux memory overcommit

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