pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Andres Freund <andres@anarazel.de>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: Kyle Kingsbury <aphyr@jepsen.io>
Cc: Peter Geoghegan <pg@bowt.ie>
Cc: Kevin Grittner <kgrittn@gmail.com>
Cc: Jeff Davis <pgsql@j-davis.com>
Cc: PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Subject: Re: Potential G2-item cycles under serializable isolation
Date: Thu, 11 Jun 2020 12:47:58 -0700
Message-ID: <20200611194758.6ihcdar3inoeegkd@alap3.anarazel.de> (raw)
In-Reply-To: <20200611193023.5t4vhsdjvkrwsrgy@alap3.anarazel.de>
References: <d91de157-b590-dd4b-3585-79f4ece79dfa@jepsen.io>
	<CAH2-Wz=9szcV1CQk4ZTj2GOKdjzf_DAAbfXdssKJnxpdX3pL2A@mail.gmail.com>
	<CAH2-Wzk+FHVJvSS9VPPJ_K9w4xwqeVyfnkzYWtWrBzXJSJcMVQ@mail.gmail.com>
	<CAH2-Wzkk5CS2emjrftQXemjDVNkYSrUEXtHd-hoxBGsjSA01Ew@mail.gmail.com>
	<20200609021706.62lwps6uywkp4kxt@alap3.anarazel.de>
	<CAH2-Wz=n7P5S_+mJHaZa4EP3qM9CGidSvocy38hm+TLvhWp1-A@mail.gmail.com>
	<CAH2-Wzk=-gRrZP4mvsFeFN8VQDw2WNdS8AnJG8eX020Q7XSmMQ@mail.gmail.com>
	<0a53caa2-d568-0283-a448-96bd4d68c235@jepsen.io>
	<CA+hUKGJgSn+JF929bMpxhn21p0ArUwjs_RrxGKb2_6Fuu5J09w@mail.gmail.com>
	<20200611193023.5t4vhsdjvkrwsrgy@alap3.anarazel.de>

On 2020-06-11 12:30:23 -0700, Andres Freund wrote:
> Hi,
> 
> On 2020-06-11 17:40:55 +1200, Thomas Munro wrote:
> > +   <para>
> > +    The Repeatable Read isolation level is implemented using a technique
> > +    known in academic database literature and in some other database products
> > +    as <firstterm>Snapshot Isolation</firstterm>.  Differences in behavior
> > +    may be observed when compared with systems using other implementation
> > +    techniques.  For a full treatment, please see
> > +    <xref linkend="berenson95"/>.
> > +   </para>
> 
> Could it be worthwhile to narrow the "differences in behaviour" bit to
> read-write transactions? IME the biggest reason people explicitly use RR
> over RC is to avoid phantom reads in read-only transactions. Seems nicer
> to not force users to read an academic paper to figure that out?

But, on second thought, it might be too difficult to phrase this
concisely and correctly, given the annoying issue of SI allowing for
read-only transactions to observe violations of serializability. I don't
think that's a RR violation, but maybe it could be understood as being
about serializability too easily?





view thread (77+ messages)  latest in thread

Message-ID: <20200611194758.6ihcdar3inoeegkd@alap3.anarazel.de>
Permalink:  ../20200611194758.6ihcdar3inoeegkd@alap3.anarazel.de/
Also on:    postgresql.org/message-id/20200611194758.6ihcdar3inoeegkd@alap3.anarazel.de

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-bugs@postgresql.org
  Cc: andres@anarazel.de, thomas.munro@gmail.com, aphyr@jepsen.io, pg@bowt.ie, kgrittn@gmail.com, pgsql@j-davis.com
  Subject: Re: Potential G2-item cycles under serializable isolation
  In-Reply-To: <20200611194758.6ihcdar3inoeegkd@alap3.anarazel.de>
  References: <d91de157-b590-dd4b-3585-79f4ece79dfa@jepsen.io> <CAH2-Wz=9szcV1CQk4ZTj2GOKdjzf_DAAbfXdssKJnxpdX3pL2A@mail.gmail.com> <CAH2-Wzk+FHVJvSS9VPPJ_K9w4xwqeVyfnkzYWtWrBzXJSJcMVQ@mail.gmail.com> <CAH2-Wzkk5CS2emjrftQXemjDVNkYSrUEXtHd-hoxBGsjSA01Ew@mail.gmail.com> <20200609021706.62lwps6uywkp4kxt@alap3.anarazel.de> <CAH2-Wz=n7P5S_+mJHaZa4EP3qM9CGidSvocy38hm+TLvhWp1-A@mail.gmail.com> <CAH2-Wzk=-gRrZP4mvsFeFN8VQDw2WNdS8AnJG8eX020Q7XSmMQ@mail.gmail.com> <0a53caa2-d568-0283-a448-96bd4d68c235@jepsen.io> <CA+hUKGJgSn+JF929bMpxhn21p0ArUwjs_RrxGKb2_6Fuu5J09w@mail.gmail.com> <20200611193023.5t4vhsdjvkrwsrgy@alap3.anarazel.de> <20200611194758.6ihcdar3inoeegkd@alap3.anarazel.de>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox