ads' corner

PostgreSQL Hacking Workshop - August 2024

On August 8th and August 15th, the first two 'PostgreSQL Hacking Workshops' took place. Robert Haas previously asked on Discord for topics, and the highest vote was for 'PostgreSQL Optimizer Methodology'. The invited attendees are expected to watch the video before, and bring questions to the workshop.

PostgreSQL Berlin July 2024 Meetup

On July 16th, 2024, we had the PostgreSQL July Meetup in Berlin. Adjust hosted and Neon sponsored the Meetup in their Berlin Headquarter at Prenzlauer Berg, near the TV Tower.

Understanding VACUUM, VACUUM template0, and Transaction ID Wraparound

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.

PostgreSQL March Meetup in Berlin

On March 5th, 2024, we had the PostgreSQL March Meetup in Berlin. Zalando hosted the Meetup in their Berlin Headquarter near the Mercedes-Benz Arena.

Avoid autovacuum for entire databases

We have a database with production data for a platform and another database with a production database dump for testing queries. We also have a test database but this one has slightly different DDL, because it’s for developing new features. Now Autovacuum is running on this server and keeps vacuuming this test database.