Ants Aasma

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.

Picking between synchronus or asynchronuos replication sounds like a simple question, but it has some deep implications for durability and performance. In this talk I will discuss why you should or should not pick synchronous replication.

PostgreSQL uses snapshots to determine which transaction can see which versions of updated rows, creating an abstraction of reading from an immutable database. This mechanism has been largely unmodified for almost 2 decades.

Applications often need to display counts of search results broken down by attributes to make it easier for users to narrow down their search conditions. For example when looking for pink shoes, a system might show how many of sneaker, loafers and wellies are available in pink, as well as how many of each size and how many from each manufacturer.