Thread: Bug: Very poor query optimization by Postgres
Hello dear Postgres-Community,
First of all I’d like to thank you for providing and developing this amazingly fast database software for free!
Now to the bug:
I’ve installed the Postgres 12 Server for Windows 10 using the installer and created the tables using Java and JDBC.
The bug is that when I execute the query “select count(*) from table” in pgAdmin in the browser or through the PostgreSQL Viewer app from the Playstore, it takes a little while which is already strange and explain indeed tells me,
that Postgres is performing a sequential scan with 2 workers instead of just returning the number or rows!
This is very poor query optimization but very easy to fix on the other hand! As well as beneficial, since this kind
of query is used very often (also as a subquery).
Below is a screenshot of pgAdmin4’s output.
Regards Tobi
Attachment
Hello dear Postgres-Community,
First of all I’d like to thank you for providing and developing this amazingly fast database software for free!
Now to the bug:
I’ve installed the Postgres 12 Server for Windows 10 using the installer and created the tables using Java and JDBC.
The bug is that when I execute the query “select count(*) from table” in pgAdmin in the browser or through the PostgreSQL Viewer app from the Playstore, it takes a little while which is already strange and explain indeed tells me,
that Postgres is performing a sequential scan with 2 workers instead of just returning the number or rows!
This is very poor query optimization but very easy to fix on the other hand! As well as beneficial, since this kind
of query is used very often (also as a subquery).
Below is a screenshot of pgAdmin4’s output.
Regards Tobi
