Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YiYUr-0006C6-7l for pgsql-docs@arkaria.postgresql.org; Thu, 16 Apr 2015 01:21:37 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YiYUq-0003IJ-6Y for pgsql-docs@arkaria.postgresql.org; Thu, 16 Apr 2015 01:21:36 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YiYUp-0003IC-Bd for pgsql-docs@postgresql.org; Thu, 16 Apr 2015 01:21:35 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1YiYUk-00065x-I2 for pgsql-docs@postgresql.org; Thu, 16 Apr 2015 01:21:33 +0000 Received: from bruce by momjian.us with local (Exim 4.72) (envelope-from ) id 1YiYUi-0003x0-BN; Wed, 15 Apr 2015 21:21:28 -0400 Date: Wed, 15 Apr 2015 21:21:28 -0400 From: Bruce Momjian To: "David G. Johnston" Cc: "pgsql-docs@postgresql.org" Subject: Re: Add a new table for Transaction Isolation? Message-ID: <20150416012128.GB1672@momjian.us> References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org On Mon, Apr 13, 2015 at 08:00:38PM -0700, David G. Johnston wrote: > http://www.postgresql.org/docs/9.4/static/transaction-iso.html > > Table 13-1 shows the SQL standard isolation levels and what is and is not > guaranteed.  Then the text goes on to explain how our implementation differs > from that table.  Is there any opposition to actually adding a similar table, > 13-2, probably right after the paragraph, with the same columns, three rows, > and the corresponding possible/not-possible cell values? Yes, it does make sense to have a table that properly matches the Postgres implementation. Should I write a patch or would you like to? -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + Everyone has their own god. + -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs