From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Robert Haas <rhaas(at)postgresql(dot)org>, pgsql-committers <pgsql-committers(at)postgresql(dot)org> |
Subject: | Re: pgsql: Add regression test for 04ae11f62e643e07c411c4935ea6af46cb112aa9 |
Date: | 2016-06-17 04:55:43 |
Message-ID: | CAA4eK1KubwdK5KiAmR2hMS0Qf+Xid5CLNO1yu2-mpnjT9tcXzA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2016-06-17 12:40:59 | pgsql: Attempt to fix broken regression test. |
Previous Message | Tom Lane | 2016-06-17 03:50:48 | Re: pgsql: Add regression test for 04ae11f62e643e07c411c4935ea6af46cb112aa9 |