Re: pgsql: Add regression test for 04ae11f62e643e07c411c4935ea6af46cb112aa9

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: pgsql: Add regression test for 04ae11f62e643e07c411c4935ea6af46cb112aa9
Дата
Msg-id CA+TgmoY0Lp5420rXzOsnFZxX31BOVqdKocSemNkRDoA+oWzX+A@mail.gmail.com
обсуждение исходный текст
Ответ на Re: pgsql: Add regression test for 04ae11f62e643e07c411c4935ea6af46cb112aa9  (Amit Kapila <amit.kapila16@gmail.com>)
Ответы Re: pgsql: Add regression test for 04ae11f62e643e07c411c4935ea6af46cb112aa9  (Andres Freund <andres@anarazel.de>)
Список 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 по дате отправления:

Предыдущее
От: Robert Haas
Дата:
Сообщение: pgsql: Attempt to fix broken regression test.
Следующее
От: Robert Haas
Дата:
Сообщение: pgsql: Remove PID from 'parallel worker' context message.