Re: parallel.c is not marked as test covered - Mailing list pgsql-hackers

From Robert Haas
Subject Re: parallel.c is not marked as test covered
Date
Msg-id CA+TgmoaDFcbhNLvS+h+2=oEiAwza8AoKrtC76hn1DEk7Pz_BuQ@mail.gmail.com
Whole thread Raw
In response to Re: parallel.c is not marked as test covered  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: parallel.c is not marked as test covered  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
On Sun, Jun 19, 2016 at 11:36 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Amit Kapila <amit.kapila16@gmail.com> writes:
>> On Sun, Jun 19, 2016 at 10:10 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> Would this not result in unstable test output depending on whether the
>>> code executes in the leader or a worker?
>
>> Before doing that test, we set force_parallel_mode=1, so it should always
>> execute in worker which will ensure a stable output.
>
> No, it *might* execute in a worker.  If you can get one.

Right.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Re: [BUGS] BUG #14199: The pg_ctl status check on server start is not compatible with the silent_mode=on
Next
From: Andreas Karlsson
Date:
Subject: Re: Parallel safety tagging of extension functions