PostgreSQL 9.4 aggregate filter clauses: They do pay off
In this blog ppost we cover the impact of aggregate FILTER clauses have on performance. Find out more about aggregation filters.
Killing proper indexing: A neat idea
There are a couple of ways to kill indexing entirely. One of this ways is to apply functions or expressions. Read out in our blog.
Shrink the storage footprint of PostgreSQL data
Keep the order of your columns in mind to unleash optimization potentials and reduce the table size in your PostgreSQL database.
Logging - the hidden speedbrakes
When it comes to performance, people tend to forget some basic topics entirely. One of those topics is the impact of writing log files.
max_connections - Performance impacts
Setting max_connections to an insanely high value is not good for performance. I tried it, to see what impact it has in PostgreSQL.
Adjusting maintenance_work_mem
After testing shared_buffers recently, I decided to do a little more testing on our new office desktop PC (8 core […]
PostgreSQL 9.3 - Shared Buffers Performance (1)
A lot has been said about PostgreSQL shared buffers and performance. As my new desktop box has arrived this week […]
Common mistakes: UNION vs. UNION ALL
In my role as a PostgreSQL consultant and trainer there are a couple of issues, which pop up on a […]
Functions: The most widely ignored performance tweak
A PostgreSQL function performance can be marked as follows: VOLATILE, STABLE, IMMUTABLE or [NOT] LEAKPROOF. Undestand why.
pgbouncer: Proving the point
pgbouncer: Opening and closing a database connection over and over again is not free, but overhead worth thinking about.
