From: | Andreas Joseph Krogh <andreas(at)visena(dot)com> |
---|---|
To: | pgsql-performance(at)lists(dot)postgresql(dot)org |
Subject: | Sv: Pg10 : Client Configuration for Parallelism ? |
Date: | 2019-04-17 09:07:51 |
Message-ID: | VisenaEmail.25.35fa198f3781c296.16a2a8aa2f0@tc7-visena |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
På onsdag 17. april 2019 kl. 08:30:28, skrev <laurent(dot)dechambe(at)orange(dot)com
<mailto:laurent(dot)dechambe(at)orange(dot)com>>: Hi,
I am working on PostgreSQL 10.5 and I have a discrepancy between clients
regarding parallelism feature.
For a simple query (say a simple SELECT COUNT(*) FROM BIG_TABLE), I can see
PostgreSQL use parallelism when the query is launched from psql or PgAdmin4.
However the same query launched with DBeaver (ie connected through JDBC) does
not use parallelism.
SELECT current_setting('max_parallel_workers_per_gather') gives 10 from my
session.
Is there a client configuration that prevents from using parallelism ?
Thanks.
Laurent Set in postgresql.conf: log_statement = 'all' reload settings and
check the logs for what statemets are acutally issued. -- Andreas Joseph Krogh
CTO / Partner - Visena AS Mobile: +47 909 56 963 andreas(at)visena(dot)com
<mailto:andreas(at)visena(dot)com> www.visena.com <https://www.visena.com>
<https://www.visena.com>
From | Date | Subject | |
---|---|---|---|
Next Message | laurent.dechambe | 2019-04-17 09:22:40 | RE: Pg10 : Client Configuration for Parallelism ? |
Previous Message | Thomas Kellerer | 2019-04-17 08:33:43 | Re: Pg10 : Client Configuration for Parallelism ? |