Month: December 2016
Detecting unstable execution times in PostgreSQL
Do you have queries with unstable execution times? You have a query which is sometimes slow and sometimes just lightning fast. The question is usually: Why? Maybe this little post can be inspiring and shade some light one some of your performance issues, which might bug you in your daily life. Reasons for unstable execution […]
pg_basebackup: Creating self-sufficient backups
UPDATED September 2023: If you use transaction log shipping (or Point-In-Time-Recovery) in PostgreSQL to keep your data safe, you surely already know about pg_basebackup. The idea behind pg_basebackup is to allow users to create a binary copy of the data which can serve as the basis for Point-In-Time-Recovery. However, recently we saw some support cases […]
Trying out Postgres Bloom indexes
By Kaarel Moppel – First – if the word “Bloom” doesn’t yet resonate with you in Postgres context, I’d recommend to read my previous introductory post on the topic here. This one is a follow-up. I aim to set up a simple demo use case to exemplify “fields of application” for Bloom, and to gauge […]
So what are Bloom indexes for Postgres?
By Kaarel Moppel – A new feature called Bloom indexing (an implementation of Bloom filters) slipped in somewhat quietly with the latest 9.6 release. New index methods are pretty rare. At the moment of the release, I of course looked through the 9.6 release notes, spent a minute there, and thought – a new index […]