eljtllr5at3el"."via_id" AS "a_1303",
COUNT_DISTINCT ( "f_zendesktags_aakrjpgq72ad93i"."ticket_id_id" ) AS
"c_fb839a9bd6f2015f"
FROM
"f_zendesktags_aakrjpgq72ad93i"
INNER JOIN
"f_zendesktickets_aaeljtllr5at3el"
ON "f_zendesk
Hi,
Having a strange situation, where adding extra parallel workers
(max_parallel_workers_per_gather), the planner chooses a different plan,
with nested loops, which makes the query twice as slow. Strangely with the
COUNT_DISTINCT implementation from Tomas Vondra (
https://github.com/tvondra/count
me=0.002..0.002 rows=0 loops=7)
Index Cond: (dt_event_id = d.id)
Planning time: 0.528 ms
Execution time: 0.144 ms
On Mon, 16 Apr 2018 at 19:16 Guilherme Pereira <
guilherme.pere...@gooddata.com> wrote:
> Hope it's fine to jump in.
>
> db_sq3rjf5b7p309lq9wuqrh3qhk
Hope it's fine to jump in.
db_sq3rjf5b7p309lq9wuqrh3qhk4gy9fbw=# set
max_parallel_workers_per_gather=0;
SET
db_sq3rjf5b7p309lq9wuqrh3qhk4gy9fbw=# explain analyze SELECT count(*)
FROM f_ticketupdate_aad5jtwal0ayaax AS f
INNER JOIN
dwh_dm_aabv5kk9rxac4lz_aaonw7nchsan2n1_aad8xhr0m_aaewg8j61iagl1z
