Re: pgsql: Add regression test for 04ae11f62e643e07c411c4935ea6af46cb112aa9

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-committers <pgsql-committers(at)postgresql(dot)org>
Subject: Re: pgsql: Add regression test for 04ae11f62e643e07c411c4935ea6af46cb112aa9
Date: 2016-06-17 12:41:31
Message-ID: CA+TgmoY0Lp5420rXzOsnFZxX31BOVqdKocSemNkRDoA+oWzX+A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Fri, Jun 17, 2016 at 12:55 AM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)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

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2016-06-17 13:26:38 pgsql: Remove PID from 'parallel worker' context message.
Previous Message Robert Haas 2016-06-17 12:40:59 pgsql: Attempt to fix broken regression test.