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

From Andres Freund
Subject Re: pgsql: Add regression test for 04ae11f62e643e07c411c4935ea6af46cb112aa9
Date
Msg-id 20160617171424.a524ysqpwiblm5va@alap3.anarazel.de
Whole thread Raw
In response to Re: pgsql: Add regression test for 04ae11f62e643e07c411c4935ea6af46cb112aa9  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-committers
On 2016-06-17 08:41:31 -0400, Robert Haas wrote:
> 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.

Dull scissors actually cause much harder to sow up / heal wounds, than
sharp ones ... :P


pgsql-committers by date:

Previous
From: Robert Haas
Date:
Subject: pgsql: Fix typo.
Next
From: Robert Haas
Date:
Subject: pgsql: Update dblink extension for parallel query.