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 AAE55D1BA8B for ; Fri, 22 Aug 2003 07:10:58 -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 82246-02 for ; Fri, 22 Aug 2003 07:10:30 -0300 (ADT) Received: from NT1 (65-85-26-2.client.dsl.net [65.85.26.2]) by svr1.postgresql.org (Postfix) with ESMTP id 1FDEBD1B8DA for ; Fri, 22 Aug 2003 07:10:27 -0300 (ADT) From: To: Subject: Re: Your application Date: Fri, 22 Aug 2003 6:11:07 --0400 X-MailScanner: Found to be clean Importance: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MSMail-Priority: Normal X-Priority: 3 (Normal) MIME-Version: 1.0 Message-Id: <20030822101027.1FDEBD1B8DA@svr1.postgresql.org> X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=4.5 tagged_above=0.0 required=5.0 tests=DATE_IN_PAST_03_06, FORGED_MUA_OUTLOOK, INVALID_DATE, MIME_BOUND_NEXTPART, MISSING_MIMEOLE, NO_REAL_NAME X-Spam-Level: **** Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="iso-8859-1" X-Archive-Number: 200308/64 X-Sequence-Number: 1924 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 ; 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 ; 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 ; 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 ; 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 ; 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?= To: pgsql-docs@postgresql.org Subject: read commited Message-ID: 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