Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jgRvd-0004ow-BV for pgsql-bugs@arkaria.postgresql.org; Wed, 03 Jun 2020 11:51:29 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jgRvb-0005SV-Tu for pgsql-bugs@arkaria.postgresql.org; Wed, 03 Jun 2020 11:51:27 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jgRvb-0005SO-NI for pgsql-bugs@lists.postgresql.org; Wed, 03 Jun 2020 11:51:27 +0000 Received: from mail.verite.pro ([185.16.44.216]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jgRvY-000372-R1 for pgsql-bugs@lists.postgresql.org; Wed, 03 Jun 2020 11:51:26 +0000 Received: from genius-map.net (verite.pro [195.154.189.246]) by mail.verite.pro (Postfix) with ESMTP id 936B98C0127; Wed, 3 Jun 2020 13:42:46 +0200 (CEST) Received: by genius-map.net (Postfix, from userid 1001) id 22C8B38A07E8; Wed, 3 Jun 2020 13:51:22 +0200 (CEST) Content-Type: text/plain; charset="iso-8859-15" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: Potential G2-item cycles under serializable isolation From: "Daniel Verite" To: "Kyle Kingsbury" Cc: "PostgreSQL mailing lists" In-Reply-To: <3150072e-13b8-7655-211b-17898f894e45@jepsen.io> Date: Wed, 03 Jun 2020 13:51:19 +0200 Message-Id: <6e4c7e1d-e901-4e84-bf37-66b58d0cf8d3@manitou-mail.org> X-Mailer: Manitou v1.7.3 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Kyle Kingsbury wrote: > SQL 92 says that the difference between repeatable read and serializable = is=20 > *exactly* the prohibition of P3 ("phantom"). You're probably refering to Table-9 in SQL-92, showing that P3 can happen under Repeatable Read and cannot happen under Serializable. But it doesn't say that the *only* difference between RR and Serializable is avoiding P3. When defining P1, P2, P3, it doesn't explicitly say that these are the only anomalies that can arise from concurrency. The PG doc refers to the other cases as "serialization anomalies". Compared to the manual, https://wiki.postgresql.org/wiki/Serializable has more in-depth explanations on the specifics of PG serializable implementation. Best regards, --=20 Daniel V=E9rit=E9 PostgreSQL-powered mailer: http://www.manitou-mail.org Twitter: @DanielVerite