Re: Potential G2-item cycles under serializable isolation

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Kyle Kingsbury <aphyr(at)jepsen(dot)io>
Cc: PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: Potential G2-item cycles under serializable isolation
Date: 2020-06-05 17:04:56
Message-ID: CAH2-WzncDaX=t5u9quujKHDPkv_iiyDyN86cOqAknae4MmBBSg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Jun 5, 2020 at 10:00 AM Kyle Kingsbury <aphyr(at)jepsen(dot)io> wrote:
> After staring at a few hundred of these anomalies, I'm more confident: this
> problem seems to involve a transaction which fails to observe a logically prior
> transaction's *insert*. So far we never see a cycle involving all updates rw
> deps--there's always 2+ rw deps, and at least one involves the initial state.
> Maybe this helps narrow down the search!

It wouldn't be the first time there was such an anomaly:

https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=585e2a3b

(You probably vaguely remember this as the bug that people were
talking about at Strange loop that same year.)

--
Peter Geoghegan

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Andres Freund 2020-06-05 17:18:40 Re: pgbench bug / limitation
Previous Message Kyle Kingsbury 2020-06-05 17:00:18 Re: Potential G2-item cycles under serializable isolation