Pg10 : Client Configuration for Parallelism ? - Mailing list pgsql-performance

From
Subject Pg10 : Client Configuration for Parallelism ?
Date
Msg-id 32277_1555482629_5CB6C805_32277_8_1_A971FB43DFBC3D4C859ACB3316C9FF4632D98B37@OPEXCAUBM42.corporate.adroot.infra.ftgroup
Whole thread Raw
Responses Re: Pg10 : Client Configuration for Parallelism ?  (Andreas Kretschmer <andreas@a-kretschmer.de>)
Re: Pg10 : Client Configuration for Parallelism ?  (Thomas Kellerer <spam_eater@gmx.net>)
Sv: Pg10 : Client Configuration for Parallelism ?  (Andreas Joseph Krogh <andreas@visena.com>)
List pgsql-performance
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
islaunched 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


_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.


pgsql-performance by date:

Previous
From: Jean-David Beyer
Date:
Subject: Re: Out of Memory errors are frustrating as heck!
Next
From: Gavin Flower
Date:
Subject: Re: Out of Memory errors are frustrating as heck!