Re: [HACKERS] intermittent failures in Cygwin from select_parallel tests
От | Robert Haas |
---|---|
Тема | Re: [HACKERS] intermittent failures in Cygwin from select_parallel tests |
Дата | |
Msg-id | CA+TgmoaSZdOLd-zC-0KecAZb1yjRkXPX8MOdX06g-zi9smCv=g@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] intermittent failures in Cygwin from select_parallel tests (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: [HACKERS] intermittent failures in Cygwin from select_parallel tests
|
Список | pgsql-hackers |
On Thu, Jun 15, 2017 at 10:38 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Robert Haas <robertmhaas@gmail.com> writes: >> On Thu, Jun 15, 2017 at 10:32 AM, Tom Lane <tgl@sss.pgh.pa.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
В списке pgsql-hackers по дате отправления: