Date: Mon, 9 Mar 2020 20:41:51 +0100 (CET)
From: Fabien COELHO <coelho@cri.ensmp.fr>
To: Thomas Munro <thomas.munro@gmail.com>
cc: Marina Polyakova <m.polyakova@postgrespro.ru>,
    Alvaro Herrera <alvherre@2ndquadrant.com>,
    pgsql-hackers <pgsql-hackers@postgresql.org>,
    Ildus Kurbangaliev <i.kurbangaliev@postgrespro.ru>,
    Teodor Sigaev <teodor@sigaev.ru>
Subject: Re: [HACKERS] WIP Patch: Pgbench Serialization and deadlock errors
In-Reply-To: 
 <CA+hUKGKBTdhanHJd4Y+opANz4Fs+VeOAbFG7TsM=tK+EBWKP4g@mail.gmail.com>
Message-ID: <alpine.DEB.2.21.2003092038190.7227@pseudo>
References: <20181116195952.nq4ak4r7cbzvoher@alvherre.pgsql>
 <f900fd87b5c58a0ff71c1f08f3c91e5f@postgrespro.ru>
 <CA+hUKGKBTdhanHJd4Y+opANz4Fs+VeOAbFG7TsM=tK+EBWKP4g@mail.gmail.com>
User-Agent: Alpine 2.21 (DEB 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Precedence: bulk


Hello Thomas,

>> Thank you very much! I'm going to send a new patch set until the end of
>> this week (I'm sorry I was very busy in the release of Postgres Pro
>> 11...).
>
> Is anyone interested in rebasing this, and summarising what needs to
> be done to get it in?  It's arguably a bug or at least quite
> unfortunate that pgbench doesn't work with SERIALIZABLE, and I heard
> that a couple of forks already ship Marina's patch set.

I'm a reviewer on this patch, that I find a good thing (tm), and which was 
converging to a reasonable and simple enough addition, IMHO.

If I proceed in place of Marina, who is going to do the reviews?

-- 
Fabien.