From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: intermittent failures in Cygwin from select_parallel tests |
Date: | 2017-06-15 14:39:48 |
Message-ID: | CA+TgmoaSZdOLd-zC-0KecAZb1yjRkXPX8MOdX06g-zi9smCv=g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jun 15, 2017 at 10:38 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> On Thu, Jun 15, 2017 at 10:32 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> It's fairly hard to read this other than as telling us that the worker was
>>> launched for the EXPLAIN (although really? why aren't we skipping that if
>>> EXEC_FLAG_EXPLAIN_ONLY?), ...
>
>> Uh, because ANALYZE was used?
>
> ... er, -ENOCAFFEINE. Nonetheless, there are no checks of
> EXEC_FLAG_EXPLAIN_ONLY in any parallel-query code, so I think
> a bet is being missed somewhere.
ExecGather() is where workers get launched, and that ain't happening
if EXEC_FLAG_EXPLAIN_ONLY is set, unless I am *very* confused about
how this works.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2017-06-15 14:49:20 | Re: logical replication: \dRp+ and "for all tables" |
Previous Message | Tom Lane | 2017-06-15 14:38:22 | Re: intermittent failures in Cygwin from select_parallel tests |