Find and fix a missing PostgreSQL Index
Explains how to find a missing Postgresql index, what you can do to fix missing indexes, and how to achieve good database performance.
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 […]
Pipeline mode for better PostgreSQL performance on slow networks
by
Laurenz Albe |
03.2022 It is known that high network latency is bad for database performance. PostgreSQL v14 has introduced “pipeline mode” for […]
Automatic partition creation in PostgreSQL
by
Laurenz Albe |
02.2022 Table partitioning is one of the best-liked features out of the more recent PostgreSQL developments. However, there is no […]
Entity-attribute-value (EAV) design in PostgreSQL - don't do it!
by
Laurenz Albe |
11.2021 Customers have often asked me what I think of “Entity-attribute-value” (EAV) design. So I thought it would be a […]
PostgreSQL: Create indexes after bulk loading
This post describes when to create indexes, before or after bulk loading of the data. Improve your PostgreSQL performance by doing it right.
Index bloat reduced in PostgreSQL v14
by
Laurenz Albe |
09.2021 PostgreSQL v12 brought more efficient storage for indexes, and v13 improved that even more by adding deduplication of index […]
PostgreSQL: The power of a SINGLE missing index
This poem post shows the importance of even one missing index for a target PostgreSQL table from a performance perspective.
PostgreSQL vs Redis vs Memcached performance
PostgreSQL vs Redis vs Memcached: How would it look on the performance side, if one just skips the cache & hits the database directly?
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.
