On Thu, Nov 30, 2017 at 2:32 PM, Michael Paquier
<michael.paquier@gmail.com> wrote:
> On Fri, Nov 24, 2017 at 1:06 PM, Haribabu Kommi
> <kommi.haribabu@gmail.com> wrote:
>> The latest patch is good. It lacks a test that verifies the serialize
>> support with actual parallel workers, so in case if it broken, it is
>> difficult to know.
>
> Could this question be answered? The patch still applies so I am
> moving it to next CF.
Thanks. The answer is: It does run queries in two different
backends, proving that different backends associated with the same
session are correctly detecting conflicts and enabling the SSI
algorithm to work. But yeah, Haribabu is right that it doesn't ever
cause them to run simultaneously in a way that would cause the new
locking to contend (or break if the locking code is incorrect). I
have been unable to think of a good way to do that in a regression or
isolation test so far.
--
Thomas Munro
http://www.enterprisedb.com
