Re: An isolation test for SERIALIZABLE READ ONLY DEFERRABLE

From: Craig Ringer <craig(dot)ringer(at)2ndquadrant(dot)com>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>
Subject: Re: An isolation test for SERIALIZABLE READ ONLY DEFERRABLE
Date: 2017-01-16 09:37:09
Message-ID: CAMsr+YFp_-phv_-92G9ENLeTF35=gq0FRz4auF3S9UMYRUW-Wg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 16 Jan. 2017 17:09, "Michael Paquier" <michael(dot)paquier(at)gmail(dot)com> wrote:

On Mon, Jan 16, 2017 at 9:40 AM, Thomas Munro
<thomas(dot)munro(at)enterprisedb(dot)com> wrote:
> I also have longer term plans to show the first and third of them
> running with the read-only transaction moved to a standby server.
> Kevin Grittner gave me the idea of multi-server isolation tests when I
> mentioned my WIP SERIALIZABLE DEFERRABLE-on-standbys patch off-list,

Being able to do that with the isolation tester has been mentioned a
coupled of times, particularly from 2ndQ folks who worked in BDR. I
think that it has been actually patched in this sense, so perhaps you
could reuse the work that has been done there.

Yep. See the bdr-pg/REL9_4_STABLE branch of the BDR repo,
src/test/isolation .

I think Abhijit submitted a patch to the list too.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2017-01-16 09:57:03 Re: Typo in condition_variable.c
Previous Message Masahiko Sawada 2017-01-16 09:34:34 Re: Typo in condition_variable.c