Teresa Lopes

Vacuum gets a bad reputation and other RDBMS vendors are quick to point it out as a PostgreSQL flaw - and yet PostgreSQL keeps getting more and more popular, year after year. Vacuum is a design decision, not an accident - Fast writes now, clean up later.

We kick off with a short DEV/DBA/DBRE panel discussion to surface the most common “Postgres at scale” failures. Then the mic is open: attendees can step up for a lightning confession : A real production “obvious fix” that backfired, the metric that proved it, and what they’d do differently.

Good technical ideas, solutions, and projects get lost when they are not well communicated. Think about losing track of a presentation because you don't know where it is going, or a software feature request where the developers reject it because they don't know why it is needed or which problem it solves.

Picture this: you start a new role, eager to learn and contribute with your ideas! Your next task is to get familiar with the database setup, and then you start encountering these massive PostgreSQL databases — 100TB, 200TB, 300TB…

Picture this: you start a new role, eager to learn and contribute with your ideas! Your next task is to get familiar with the database setup, and then you start encountering these massive PostgreSQL databases — 100TB, 200TB, 300TB...