Query performance of the upcoming version 11 of PostgreSQL
Release notes of first RC of PostgreSQL 11 didn't state any numerical query performance indicators, so we have to find it out on our own.
3 ways to detect slow queries in PostgreSQL
How to fix bad performance in PostgreSQL - shows three useful and quick methods to spot performance problems and slow queries.
Avoiding “OR” for better query performance
by
Laurenz Albe |
05.2018 PostgreSQL query tuning is our daily bread at CYBERTEC, and once you have done some of that, you'll start […]
Using "lightweight" functional indexes - BRIN
When it alters columns in queries, Postgres loses statistics, and it can cause slow queries. Fix it with BRIN functional indexes.
Parallel queries and SERIALIZABLE transactions
In version 9.6 PostgreSQL introduced parallel queries. The ability to use more than just one CPU core per query is […]
Detecting wrong planner estimates
The PostgreSQL planner optimizes your queries, and mostly does it right. The question is: How to figure out when & where things do go wrong?
effective_cache_size: Better set it right
effective_cache_size can have a serious impact on execution plans and change things dramatically. See what kind of difference it can make.
Speeding up “min” and “max”
In this blog you can read why indexes are a great tool. And how it is possible speeding up a query many times by avoiding a sequential scans,
