Re: pgsql: Add regression test for 04ae11f62e643e07c411c4935ea6af46cb112aa9 - Mailing list pgsql-committers

From Robert Haas
Subject Re: pgsql: Add regression test for 04ae11f62e643e07c411c4935ea6af46cb112aa9
Date
Msg-id CA+TgmoY0Lp5420rXzOsnFZxX31BOVqdKocSemNkRDoA+oWzX+A@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: Add regression test for 04ae11f62e643e07c411c4935ea6af46cb112aa9  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: pgsql: Add regression test for 04ae11f62e643e07c411c4935ea6af46cb112aa9  (Andres Freund <andres@anarazel.de>)
List pgsql-committers
On Fri, Jun 17, 2016 at 12:55 AM, Amit Kapila <amit.kapila16@gmail.com> wrote:
> 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;

Yeah, I can't believe I managed to be dumb enough to think that was
going to work.

Clearly, I shouldn't be trusted with anything more dangerous than a
dull pair of scissors.

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


pgsql-committers by date:

Previous
From: Robert Haas
Date:
Subject: pgsql: Attempt to fix broken regression test.
Next
From: Robert Haas
Date:
Subject: pgsql: Remove PID from 'parallel worker' context message.