CLUSTER: Improving PostgreSQL performance
Learn an important trick to lower the performance impact of data storage methods in your PostgreSQL database. Use CLUSTER to improve speed.
Reduce WAL by increasing checkpoint distance
Adjusting checkpoints is useful when tuning a server and improves the database performance. Furthermore, it helps to reduce WAL.
shared_buffers: Looking into the PostgreSQL I/O cache
shared_buffers: What does the PostgreSQL I/O cache contain? Find out what the cache knows about your database.
PostgreSQL: You might need to increase max_locks_per_transaction
How can you prevent the error "out of shared memory" in PostgreSQL? max_locks_per_transaction is the critical configuration parameter.
Setting PostgreSQL configuration parameters
PostgreSQL configuration offers more than meets the eye at first glance, so let us dive into PostgreSQL configuration parameters.
effective_cache_size: What it means in PostgreSQL
effective_cache_size is usefull for database tuning as well als for speeding up PostgreSQL. Learn more about of this secretive setting.
Never lose a PostgreSQL transaction with pg_receivewal
by
Laurenz Albe |
10.2019 “Durability”, the D of ACID, demands that a committed database transaction remains committed, no matter what. For normal […]
Prewarming PostgreSQL I/O caches
How to deal with PostgreSQL restarts? pg_prewarm allows you to automatically prewarm your caches after a database failure or a simple restart
What is autovacuum doing to my temporary tables?
The main issue is that autovacuum does not touch temporary tables. Yes, it’s true – you have to VACUUM temporary tables on your own. Read more
Fixing track_activity_query_size in postgresql.conf
How to use track_activity_query_size, a configuration parameter that determines when a query will be cut off. Use it to your advantage.
