Enforcing join orders in PostgreSQL
PostgreSQL handle joins & especially join orders? Internally the PostgreSQL does a good job to optimize queries but how does it really work?
Different from many other database systems, PostgreSQL does not support query hints. That makes it difficult to force the […]
Rewrite OR to UNION in PostgreSQL queries
by
Laurenz Albe |
11.2022 In my article that reviles OR, I showed how in certain cases, it is possible to rewrite OR in […]
Query parameter data types and performance
by
Laurenz Albe |
03.2022 Recently, I could help solve a “mysterious” performance problem for a customer. The problem turned out to be a […]
Data warehousing: Making use of synchronized seq scans
Did you know PostgreSQL has the ability to synchronize sequential scans? If you are running data warehouses, you might have already used it without knowing.
How to interpret PostgreSQL EXPLAIN ANALYZE output
by
Laurenz Albe |
05.2021 UPDATED July 2023: EXPLAIN ANALYZE is the key to optimizing SQL statements in PostgreSQL. This article does not attempt […]
Detecting unstable execution times in PostgreSQL
How to tune a query which is sometimes slow and sometimes fast. The question is usually: How come it has an unstable execution time?
paginators - The story about voluntary pain in PostgreSQL
If you want to display millions of entries on your website, you definitely turn to paginators. Here's how you do it right using PostgreSQL.
Spying on slow statements with “auto_explain”
PostgreSQL "auto_explain" functionality is a useful debugging helper that many people don't know about. Describes setup and use cases.
Beating Uber with a PostgreSQL prototype
How to beat the latency of Uber's geo-fencing query by just using nice PostgreSQL code and 30 minutes of programming time.