ads' corner

This blog posting is part of a series about organizing Meetups. You are speaking at a Meetup. Congratulations! Here are some recommendations.

A review of FOSDEM 2025 and the FOSDEM PGDay 2025

On February 4th, 2025, we had the PostgreSQL February Meetup in Berlin. This time Zalando hosted it again, and we did something big: two tracks, two lightning talks and four regular talks. Oh, and about 130 attendees. That is already a mini conference!

The PostgreSQL Project is present with a booth at FOSDEM ever since 2007. And ever since 2008 we organize a Devroom, starting 2013 we also have our own PGDay on the Friday before FOSDEM. This year it's the 11th FOSDEM PGDay, skipping 2021 and 2022 for obvious reasons. This blog post provides useful information for visitors of the PGDay, the booth and the PostgreSQL Devroom at FOSDEM.

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.

On October 9th, 2024, we had the PostgreSQL October Meetup in Berlin. Amazon hosted it. Josef Machytka spoke about JSON, Aychin Gasimov spoke about new features in PostgreSQL 17.

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.

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.

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.