PostgreSQL is in case of more complex queries or views much faster than MySql.
We were having performance problems with project using MySql (fine tuned, but using views. project has been using it over 2 years).
After test rewriting of some problematic queries to PostgreSQL and query testing, I was quite shocked.
query time with mysql was 1.7 second.... and in postgresql 65ms!!!
after that, we rewrote entire project to postgres and it is indeed significiantly faster at all
Comment - such situation can occur in specific conditions, which were, though, quite common in our project. There were:
- need to use views (usually complex queries)
- tables with many records (not so many, actually thousands), while selecting only top x
I tried to find out how is this possible and the result was clear, based on both DBMS docs - very poor implementation of views in mysql. Most of complex queries fall into 'temptable' type, which means that temporary table is created every time query is executed.
PostgreSQL is in case of
PostgreSQL is in case of more complex queries or views much faster than MySql.
We were having performance problems with project using MySql (fine tuned, but using views. project has been using it over 2 years).
After test rewriting of some problematic queries to PostgreSQL and query testing, I was quite shocked.
query time with mysql was 1.7 second.... and in postgresql 65ms!!!
after that, we rewrote entire project to postgres and it is indeed significiantly faster at all
Comment - such situation can occur in specific conditions, which were, though, quite common in our project. There were:
- need to use views (usually complex queries)
- tables with many records (not so many, actually thousands), while selecting only top x
I tried to find out how is this possible and the result was clear, based on both DBMS docs - very poor implementation of views in mysql. Most of complex queries fall into 'temptable' type, which means that temporary table is created every time query is executed.