ads' corner

While testing a new feature for WarehousePG in our Docker containers, I ran into an unexpected problem: I wanted to block certain network traffic between the Docker hosts, and therefore installed nftables. Suddenly very early in the startup process the ssh-copy-id ssh key exchange broke.

This was my first time attending PGConf.India. Something I wanted to do for quite a while, heard good things about the conference. but never had a chance before. The conference is well attended, and very vibrant. Good presentations, a lot of questions about *WarehousePG* (the talk I gave) and about *PostgreSQL* in general.

A recent blog posting by Frédéric Delacourt reminded me once again that in the analytics world customers sometimes ask for more than 1600 columns. But is that even possible?

Back in July I submitted talks to the annual PostgreSQL Conference Japan 2025 (PostgreSQL カンファレンス 2025). This year is the 20th year of the conference, I was told. To my surprise, one of my submitted talks was accepted.

This blog posting has a detailed explanation how the TDE performance test was conducted.

This blog posting compares the performance of the pg_tde by Percona extension for PostgreSQL with the performance of an unmodified PostgreSQL. The pg_tde by Percona extension provides encryption for both data pages on disk as well as WAL files on disk - Encryption at Rest.

On Monday before PGConf.dev, the Postgres Extensions Day 2025 took place. Same venue, same floor. A day fully packed with talks, and interesting discussions.

PGConf.EU 2024 in Athens is over - time to look back and recap the conference. It was the largest PostgreSQL conference organized by PostgreSQL Europe - so far.

Lightning Talks at PGConf.EU are always fun. This year, more people had a chance to submit a talk. Note: many pictures inside.

PostgreSQL uses Multi-Version Concurrency Control (MVCC) to manage concurrent access to the database, and store each version of a tuple in a table. To keep the database efficient, PostgreSQL employs a cleanup process called VACUUM, which removes unnecessary tuples. This not only saves disk space and keeps the database size under control, it also prevents the dreaded 'Transaction ID Wraparound' issue. Regularly running VACUUM is crucial, including on the template0 database, which is normally handled by the Autovacuum daemon. However, sometimes manual intervention is necessary.