Re: pgsql: Add regression test for 04ae11f62e643e07c411c4935ea6af46cb112aa9

On Fri, Jun 17, 2016 at 9:20 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Robert Haas <rhaas(at)postgresql(dot)org> writes:
> > Add regression test for 04ae11f62e643e07c411c4935ea6af46cb112aa9.
>
> BTW, the buildfarm thinks this test fails a lot of the time, and
> running "make installcheck-parallel" a few times here agrees: it
> falls over more than 20% of the time. Don't know why it would be
> probabilistic,
>

I also got failure with this test on my m/c:
select parallel_restricted(unique1) from tenk1
where stringu1 = 'GRAAAA' order by 1;
ERROR: parallel restricted function run in worker
CONTEXT: PL/pgSQL function parallel_restricted(integer) line 5 at RAISE

Isn't it possible that the below statement used in parallel restricted
function fails in leader backend itself:
+ perform * from pg_stat_activity where client_port is null;
+ if (found) then
+ raise 'parallel restricted function run in worker';
+ end if;

With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com