#5 PostgreSQL Meetup Vienna

The 5th PostgreSQL Meetup in Vienna is coming up!
Exciting talks and networking opportunities around PostgreSQL are waiting for you.
Meet fellow Vienna-based and international PostgreSQL enthusiasts at this meetup and take the opportunity to connect locally and exchange ideas.

When: 12 October, 2026 — 6:30 PM to 9:30 PM
Where: TBD

Preliminary Agenda:
6:30–7:00 PM — Doors open & registration, networking & Pizza
7:00–7:15 PM — Welcome & Sponsor introduction
7:15–7:45 PM — Talk 1: My Dishonest Benchmark: How to Manufacture a 100x PostgreSQL Performance Claim, by Mayuresh B.
7:45–8:00 PM — Break
8:00-8:30 PM - Talk 2: DIY Postgres Branching, by Radim Marek
8:30-8:45 PM - Break
8:45–9:00 PM —Lightning Talks (TBD) / Community Updates
9:00–9:10 PM — Closing
9:10–9:30 PM — Networking & Snacks

**************
Talk 1: My Dishonest Benchmark: How to Manufacture a 100x PostgreSQL Performance Claim, by Mayuresh B.
Postgres has no owner.
There is no Postgres marketing department.
There is no Postgres PR strategy.
Meanwhile, competitors keep publishing colorful performance graphs to impress any CIO or CTO.
This is unfair.
So let us do what Postgres does not usually do.
Let us create a benchmark that makes Postgres look absurdly fast.
In this talk, I take a small TPC-C-inspired workload and manufacture an apparent 100x performance ladder. We start with a deliberately crippled baseline, while also using it separately to illustrate how an honestly framed benchmark should be presented. We then tinker with the client protocol, sacrifice crash safety, play with durability knobs, move work into server-side functions, and inflate the operations per second number through pipelining and batching.
Every reported number is technically real. The framing is the dishonest part.
We do whatever it takes to present a heroic Postgres.
Along the way, I will briefly revisit the old database benchmark wars and the DeWitt clause, because that history explains why weak benchmark claims survive so easily and why this talk is necessary.

Talk 2: DIY Postgres Branching, by Radim Marek

Snacks and drinks will be provided.
🚨 Attention: Limited spots available! 🚨

Please mind the PostgreSQL Community Code of Contact: https://www.postgresql.org/about/policies/coc/