pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Kyle Kingsbury <aphyr@jepsen.io>
To: Peter Geoghegan <pg@bowt.ie>
Cc: PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Subject: Re: Potential G2-item cycles under serializable isolation
Date: Wed, 3 Jun 2020 12:44:42 -0400
Message-ID: <586286c6-b4dc-7257-efdd-ba1eb8f62dcc@jepsen.io> (raw)
In-Reply-To: <4e63a8e6-41c9-2a62-b780-2b56005d2253@jepsen.io>
References: <db7b729d-0226-d162-a126-8a8ab2dc4443@jepsen.io>
	<CAH2-WzkmEz0ax0AG_nc788uRSe_P_RTQwgkveY5VCjDy5y4eUw@mail.gmail.com>
	<11bb3199-c685-1cec-63bb-f92848edbe10@jepsen.io>
	<CAH2-Wzne1fr47aayESfDdfMvjiB+jSfW+xEWggdZuRYa8CL8Nw@mail.gmail.com>
	<CAMotZ_w2-bdQms+rFa-DA_vH+y7A=ky0Gmwu9Y81LT=2ge5TtQ@mail.gmail.com>
	<CAH2-WzkBwwDj38NvdiP4J3ia_POC68C1-FCtXvnDvnzwMASv5w@mail.gmail.com>
	<54c6c503-b939-c4ce-0d54-4f998ac04168@jepsen.io>
	<CAH2-Wzm2F+pNUVeonrS3cZfttJDBmp0nMUiHYG4qAoGQO-rCvA@mail.gmail.com>
	<3150072e-13b8-7655-211b-17898f894e45@jepsen.io>
	<CAH2-WzmD__iOD-zBNDU07ZDQkha36cJ5aXdxB8BYW6=bWR2oqg@mail.gmail.com>
	<b1187ab1-1946-ff78-163d-ff76974e1902@jepsen.io>
	<CAH2-WzkR4qpHOcirynHd1=xoo05T6vYLSzYHV_GWU0wQysJU_A@mail.gmail.com>
	<CAH2-Wz=cYfUSXEUJkWf=xgXdmCTCgqNRKGg1LvbiKLmRvtQTNw@mail.gmail.com>
	<4e63a8e6-41c9-2a62-b780-2b56005d2253@jepsen.io>

On 6/3/20 10:20 AM, Kyle Kingsbury wrote:
> On 6/2/20 7:17 PM, Peter Geoghegan wrote:  >> It seems kind of inconvenient to run Jepsen -- I suppose I could >> use 
Docker or something like that, but I don't have experience >> with it. What do 
you think is the simplest workflow for somebody >> that just wants to recreate 
your result on a Debian system? > > I'll see about writing a version of the test 
that doesn't use any of > the automation, so you can point it at a local 
postgres instance. > Then all you'll need is lein and a jdk.
OK, I think we're all set. With Jepsen 0ec25ec3, you should be able to run:

cd stolon;

lein run test-all -w append --max-writes-per-key 4 --concurrency 50 -r 500 
--isolation serializable --time-limit 60 --nemesis none --existing-postgres 
--node localhost --no-ssh --postgres-user jepsen --postgres-password pw

... and it'll connect to an already-running instance of Postgres on localhost 
(or whatever you want to connect to) using the provided username and password. 
It expects a DB with the same name as the user. You'll need a JDK (1.8 or 
higher), and Leiningen (https://leiningen.org/), which should be pretty easy to 
install. :)

> Could you test Postgres 9.5? It would be nice to determine if this  > is a new issue, or a regression.

I can also confirm that Postgres 9.5.22, 10.13, and 11.8 all exhibit the same 
G2-item anomalies as 12.3. It looks like this issue has been here a while! 
(Either that, or... my transactions are malformed?).

Is there additional debugging data I can get you that'd be helpful? Or if you'd 
like, I can hop in an IRC or whatever kind of chat/video session you'd like to 
help you get these Jepsen tests running.

--Kyle

view thread (77+ messages)  latest in thread

Message-ID: <586286c6-b4dc-7257-efdd-ba1eb8f62dcc@jepsen.io>
Permalink:  ../586286c6-b4dc-7257-efdd-ba1eb8f62dcc@jepsen.io/
Also on:    postgresql.org/message-id/586286c6-b4dc-7257-efdd-ba1eb8f62dcc@jepsen.io

 · 

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: aphyr@jepsen.io, pg@bowt.ie
  Subject: Re: Potential G2-item cycles under serializable isolation
  In-Reply-To: <586286c6-b4dc-7257-efdd-ba1eb8f62dcc@jepsen.io>
  References: <db7b729d-0226-d162-a126-8a8ab2dc4443@jepsen.io> <CAH2-WzkmEz0ax0AG_nc788uRSe_P_RTQwgkveY5VCjDy5y4eUw@mail.gmail.com> <11bb3199-c685-1cec-63bb-f92848edbe10@jepsen.io> <CAH2-Wzne1fr47aayESfDdfMvjiB+jSfW+xEWggdZuRYa8CL8Nw@mail.gmail.com> <CAMotZ_w2-bdQms+rFa-DA_vH+y7A=ky0Gmwu9Y81LT=2ge5TtQ@mail.gmail.com> <CAH2-WzkBwwDj38NvdiP4J3ia_POC68C1-FCtXvnDvnzwMASv5w@mail.gmail.com> <54c6c503-b939-c4ce-0d54-4f998ac04168@jepsen.io> <CAH2-Wzm2F+pNUVeonrS3cZfttJDBmp0nMUiHYG4qAoGQO-rCvA@mail.gmail.com> <3150072e-13b8-7655-211b-17898f894e45@jepsen.io> <CAH2-WzmD__iOD-zBNDU07ZDQkha36cJ5aXdxB8BYW6=bWR2oqg@mail.gmail.com> <b1187ab1-1946-ff78-163d-ff76974e1902@jepsen.io> <CAH2-WzkR4qpHOcirynHd1=xoo05T6vYLSzYHV_GWU0wQysJU_A@mail.gmail.com> <CAH2-Wz=cYfUSXEUJkWf=xgXdmCTCgqNRKGg1LvbiKLmRvtQTNw@mail.gmail.com> <4e63a8e6-41c9-2a62-b780-2b56005d2253@jepsen.io> <586286c6-b4dc-7257-efdd-ba1eb8f62dcc@jepsen.io>

* 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