Month: July 2020
effective_cache_size: A practical example
A lot has been written about effective_cache_size in postgresql.conf and about PostgreSQL performance in general. However, few people know what this famous parameter really does. Let me share some more insights. What the PostgreSQL optimizer does The idea behind SQL is actually quite simple: The end user sends a query and the optimizer is supposed […]
What is fillfactor and how does it affect PostgreSQL performance?
By Kaarel Moppel Recently I was asked if there’s a rule of thumb / best practice for setting the fillfactor in Postgres – and the only answer I could give was to decrease it “a bit” if you do lots and lots of updates on some table. Good advice? Well, it could be better – […]
PostgreSQL: More performance for LIKE and ILIKE statements
LIKE and ILIKE are two fundamental SQL features. People use those things all over the place in their application and therefore it makes sense to approach the topic from a performance point of view. What can PostgreSQL do to speed up those operations and what can be done in general to first understand the problem […]
pgwatch2 v1.8.0 released
After exactly half a year (seems to be a pattern already) since the last major release of pgwatch2 Open Source PostgreSQL monitoring tool, I’m glad to announce that another set of useful features and improvements have found their way into the pgwatch2 code repository! The new version is incremented to v1.8.0 and content-wise, it’s mostly […]
pg_timetable: start-up improvements
¡Hola, queridos amigos! We’ve released several valuable features for pg_timetable in May. It’s summer already, and time is flying fast! I hope all of you are well and safe, as well as your families and friends. Here I want to introduce what’s new and how that is useful briefly. If you are unfamiliar with pg_timetable, […]
PostgreSQL: Useful new data types – CREATE DOMAIN
UPDATED 08.05.2023 – SQL and especially PostgreSQL provide a nice set of general purpose data types you can use to model your data. However, what if you want to store fewer generic data? What if you want to have more advanced server-side check constraints? The way to do that in SQL and in PostgreSQL in […]