Reducing log messages on the client
Frequently PostgreSQL client applications are flooded with log messages from the server. Correct this by changing the server configuration.
The power of response times and execution time
The goal of the PostgreSQL optimizer is to provide a plan which executes as fast as possible & returns all the data as rapidly as possible.
wal_level: What is the difference?
PostgreSQL replication requires changing the wal_level from “minimal” to “hot_standby”. What er the impacts? Read out more.
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 […]
Security barriers: Cheating on the planner
UPDATED Aug. 2023 - How a security barrier can theoretically be used to speed up PostgreSQL queries and to see how PG works under the hood.
Detecting table bloat in PostgreSQL
If your PostgreSQL database is badly structured, you might face some table bloat. Figure out if a table is bloated or not.
Functions: The most widely ignored performance tweak
A PostgreSQL function performance can be marked as follows: VOLATILE, STABLE, IMMUTABLE or [NOT] LEAKPROOF. Undestand why.
