Name: PostgreSQL Berlin June Meetup
Start: 2025-06-19T18:30:00+02:00
End: 2025-06-19T21:30:00+02:00
Location: MD-IT GmbH

MD-IT GmbH offered to host us for a Meetup. We again have two meeting rooms, and room for four talks, two parallel tracks. The number of seats is limited, please only sign up if you plane to come. Once we reach the waitlist we will control seats by bumping anyone to the end of the list who signed up in the past and did not show up.

**Pizza and Soft Drinks will be kindly provided by MD-IT.**

**Our speakers and talks:**

Stefanie Janine Stölting (ProOpenSource): PostgreSQL as Data Integration tool.

Sergey Dudoladov (Zalando): The Lifecycle of a SELECT: A Glimpse into the Depths of PostgreSQL Internals.

Artur Zakirov (Supabase): What Is Dead May Roll Back: Undo Logging in OrioleDB.

Josef Machytka (Credativ): Database in Distress: Testing and Repairing Different Types of Database Corruption. Josef will also present a lightning talk "Boldly Migrate to PostgreSQL — Introducing credativ-pg-migrator".

**Agenda:**

18:30 - 19:00 - Doors open: registration and networking.
19:00 - 19:10 - Opening and MD-IT introduction.
19:15 - 20:00 - Track 1: PostgreSQL as Data Integration tool.
19:15 - 20:00 - Track 2: What Is Dead May Roll Back: Undo Logging in OrioleDB.
20:00 - 20:30 - Pizza break and networking.
20:30 - 21:15 - Track 1: The Lifecycle of a SELECT: A Glimpse into the Depths of PostgreSQL Internals.
20:30 - 21:15 - Track 2: Database in Distress: Testing and Repairing.
21:15 - 21:20 - Closing.

**Abstracts**

*PostgreSQL as Data Integration tool*

Instead of using ETL Tools, which consume tons of memory on their own system, you will learn how to do ETL jobs directly in and with a database. The PostgreSQL implementation of the the standard ISO/IEC 9075-9:2016, Management of External Data ([SQL/MED](https://www.iso.org/standard/63476.html)), is also known as Foreign Data Wrapper (FDW). With Foreign Data Wrapper, there is nearly no limit of external data, that you could use directly inside a PostgreSQL database.
The talk will walk you through the definition of Foreign Data Wrapper as implemented in PostgreSQL. In the second part of the talk you will see how this technology does work shown by examples with several data sources.

*The Lifecycle of a SELECT: A Glimpse into the Depths of PostgreSQL Internals*

PostgreSQL practitioners often advise developers with recommendations like "Always use EXPLAIN ANALYZE with BUFFERS" or "Run ANALYZE first". However, these suggestions are rarely accompanied by clear explanations of why they matter. Inspired by the motto "Knowledge of certain principles easily compensates for the lack of knowledge of certain facts," this talk sheds light on key PostgreSQL architectural concepts and their connection to common design and performance best practices.
Through a series of increasingly complex SELECT queries, we will explore how PostgreSQL’s internal mechanisms enable safe, fast, and efficient data processing. This session is designed for application developers who want to deepen their understanding of how PostgreSQL executes queries— and how to harness its full potential without accidentally bringing it to its knees.

*What Is Dead May Roll Back: Undo Logging in OrioleDB*

PostgreSQL implements transactions and MVCC using tuple versioning and a background vacuum process. This design offers simplicity of concurrency control but has trade-offs, like table and index bloat and increased maintenance complexity of the vacuum process.
OrioleDB is an alternative storage engine for PostgreSQL which introduces undo logs to implement transactions and MVCC. Undo logs offer immediate cleanup of tuples without additional vacuum process.
This talk will examine the trade-offs of PostgreSQL’s current MVCC design. Then it will introduce the concept of undo logging, explain how OrioleDB implements it. The talk will provide a technical overview of how undo logs work in OrioleDB.

*Database in Distress: Testing and Repairing Different Types of Database Corruption*

Every relation in PostgreSQL can be damaged, and sometimes the errors reported by the database are rather strange. In some cases, a session reading corrupted data can even crash the whole database. In recent years, I had to work on repairs of several corrupted PostgreSQL databases and have seen many different problems. To better understand these issues and test different strategies for repairs, I created a Python application that simulates various types of damage. This talk demonstrates, through practical examples and outputs from the pageinspect extension, different types of data corruption — and proposes some future improvements that would help handle them more effectively.

**Note**
We will again take notes who signs up and does not show up. This information will be used to provide seats to others at future events. Plain and simple: please only sign up if you plan to attend and update your response to "No" if your plans changed. This helps us offer spots to others on the waitlist.

Oleksii Kliukin

Mathias F.

Sergey Dudoladov

PostgreSQL Meetup Group Berlin

Technology

Open Source

Linux

Data

Database Professionals

PostgreSQL

Database Development

Data Management

PostgreSQL Berlin June Meetup

MD-IT GmbH

Teilen

PostgreSQL Meetup Group Berlin

PostgreSQL Berlin June Meetup

PostgreSQL Meetup Group Berlin

Details

Mitglieder interessieren sich auch für