Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Ym7PP-0008Ng-2a for pgsql-docs@arkaria.postgresql.org; Sat, 25 Apr 2015 21:14:43 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1Ym7PO-0005zW-Ht for pgsql-docs@arkaria.postgresql.org; Sat, 25 Apr 2015 21:14:42 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1Ym7PN-0005zP-Hj for pgsql-docs@postgresql.org; Sat, 25 Apr 2015 21:14:41 +0000 Received: from mail-ig0-x22c.google.com ([2607:f8b0:4001:c05::22c]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1Ym7PK-0007Dv-Dt for pgsql-docs@postgresql.org; Sat, 25 Apr 2015 21:14:40 +0000 Received: by iget9 with SMTP id t9so47667500ige.1 for ; Sat, 25 Apr 2015 14:14:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=2O3TFSOi3IP5qXd0y67VJ4xozFQk9VVCLCLtpwymVyI=; b=iJJwzmBLG3md+VXK2r0LNpACjP15wM+phWlbCKOg364s3LUT2CPTT8d2RNy3XJMo1d JgpsknvM0gphCad5kKrZljwWWLQcZvq0iKPoWJEIm8h3FiGRY6kuDTPy2XXtRtU3uw6r uSrQPmcZkA0smhD715V12k2K+C4WBdGtxpEy7xxiuqM8gcGuBiOBlYqyyLPo1ulkNCFZ IQn9O6OVTTfj5gYoM0kBpMKMzmuqrP0R7GcG2ZzOedpU9OSbXPMtsv3WbRnf1xhEqOmX tq5SMivQ1P1ikveDiY4U0KudHtwdfMYPr0h36+CzAu2sktkC8oirN55NPnkBHOOuWZ7+ mt2w== MIME-Version: 1.0 X-Received: by 10.43.178.201 with SMTP id ox9mr5344438icc.49.1429996477459; Sat, 25 Apr 2015 14:14:37 -0700 (PDT) Received: by 10.36.64.15 with HTTP; Sat, 25 Apr 2015 14:14:37 -0700 (PDT) In-Reply-To: <20150425205700.GE17791@momjian.us> References: <20150425200255.GD17791@momjian.us> <279680020.4245099.1429994867712.JavaMail.yahoo@mail.yahoo.com> <20150425205700.GE17791@momjian.us> Date: Sat, 25 Apr 2015 14:14:37 -0700 Message-ID: Subject: Re: Add a new table for Transaction Isolation? From: "David G. Johnston" To: Bruce Momjian Cc: Kevin Grittner , Peter Eisentraut , "pgsql-docs@postgresql.org" Content-Type: multipart/alternative; boundary=001a11c318de11b3f70514930066 X-Pg-Spam-Score: -2.7 (--) 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 --001a11c318de11b3f70514930066 Content-Type: text/plain; charset=UTF-8 On Saturday, April 25, 2015, Bruce Momjian wrote: > On Sat, Apr 25, 2015 at 08:47:47PM +0000, Kevin Grittner wrote: > > Maybe something like "Prohibited", "Allowed but not Possible", and > > "Possible"? That would take a little explaining above, since our > > documentation's table would be deviating from the standard's table > > in its word choice. > > I can't even process that. > > After writing my thoughts this makes sense now. Prohibited means that both tables would say not possible. Possible means both tables would say possible. Allowed but not possible means our implementation says not possible and the standard says it is possible. The fourth possibility, not allowed but possible, would mean we are not standard conforming and since we are it never appears. I would probably choose "not possible (contra-SQL)" and emphasize our implementation and footnote the two differences. David J. --001a11c318de11b3f70514930066 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Saturday, April 25, 2015, Bruce Momjian <bruce@momjian.us> wrote:
O= n Sat, Apr 25, 2015 at 08:47:47PM +0000, Kevin Grittner wrote:
> Maybe something like "Prohibited", "Allowed but not Pos= sible", and
> "Possible"?=C2=A0 That would take a little explaining above,= since our
> documentation's table would be deviating from the standard's t= able
> in its word choice.

I can't even process that.


After writing my thoughts this makes sense= now.=C2=A0 Prohibited means that both tables would say not possible.=C2=A0= Possible means both tables would say possible.=C2=A0 Allowed but not possi= ble means our=C2=A0implementation says not possible and the standard says i= t is possible.=C2=A0 The fourth possibility, not allowed but possible, woul= d mean we are not standard conforming and since we are it never appears.

I would probably choose "not possible (contra-S= QL)" and emphasize our implementation and footnote the two differences= .

David J.
--001a11c318de11b3f70514930066--