When I ran a query in Postgres database using the Pg Admin tool it took only 2 SECS ( I can see the parallel workers being used in the plan) but when I ran the same query in DBeaver, it took around 3 MINS to complete (the plan is different and I don't see yhe parallel workers being invoked. Can anybody explain why the difference in these tools? Are the drivers causing the different plan and execution time?. What is the driver PG Admin is using to connect to Postgres database?.
Postgresql – DBEaver Vs PG Admin
dbeaverpgadmin-4postgresql
Related Question
- PostgreSQL – Why Parallel pg_restore Takes Longer Than Non-Parallel?
- PostgreSQL 12 – Slower Performance Compared to PostgreSQL 9.5
- PostgreSQL Parallel Query – How to Sum Times in EXPLAIN
- PostgreSQL 11 – Query Plan Using Seq Scan After Upgrade
- Postgresql – How does Postgres decide if to use additional workers
- Comparing Query Performance Across PostgreSQL, MariaDB, and SQLite
Best Answer
Not knowing DBeaver, I can only guess: it uses a cursor to process statement results. That has two consequences:
Parallelization cannot be used:
A different execution plan may be used: