<?xml version='1.0' encoding='utf-8'?>
<schedule><version>Firefly</version><conference><title>PGConf.EU 2025</title><start>2025-10-21</start><end>2025-10-24</end><days>4</days><baseurl>https://www.postgresql.eu/events/pgconfeu2025/schedule/</baseurl></conference><day date="2025-10-21"><room name="Other"><event id="7242"><start>08:15</start><duration>00:45</duration><room>Other</room><title>Registration</title><abstract /><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7242/</url><track>PGConf.EU</track><persons /></event></room><room name="Beta 1"><event id="7154"><start>09:00</start><duration>03:30</duration><room>Beta 1</room><title>Community Summit – PGConf EU Edition</title><abstract>&lt;p class="centred"&gt;
  Community building, support, and maintenance are all critical to the future of Postgres. There are many types and layers to community building from events, podcasts, &amp; meetups to extracurricular fun like chess &amp; karaoke; recognition &amp; rewards to Postgres booths at non-Postgres conferences; getting started in smaller communities to wrangling a global one.
&lt;/p&gt;

&lt;p&gt;
  In this 3-hour summit (with 2 90-minute sessions with 4 breakouts each) we will:
&lt;/p&gt;

&lt;p&gt;
  &lt;ul&gt;
    &lt;li&gt;Perform an “unconference” like exercise to determine which aspects of community we should cover. The hosts will come armed with some teaser topics, but the group will be asked to add to the list and then vote.&lt;/li&gt;
    &lt;li&gt;Break into smaller groups to tackle areas the group believes are most important&lt;/li&gt;
    &lt;li&gt;Report out to the larger group by each small group&lt;/li&gt;
    &lt;li&gt;Each group adds their results to the PostgreSQL Wiki&lt;/li&gt;
    &lt;li&gt;Determine a way for us to track our progress moving forward&lt;/li&gt;
  &lt;/ul&gt;
&lt;/p&gt;

&lt;p&gt;
Due to the interactive nature of the summit participation is limited to 60 people. Participants should be committed to build, support, or maintain a community in some way, and be ready to leave the summit with concrete action items to move the Postgres community forward. While the hosts from this summit are from the US &amp; Europe, we hope that folks from less established Postgres communities will join us.
&lt;/p&gt;

&lt;nav class="button-bar"&gt;
    &lt;a class="button primary" href="https://2025.pgconf.eu/community-events/community-summit-pgconf-eu-edition/"&gt;Find Out More&lt;/a&gt;
&lt;/nav&gt;</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7154/</url><track>Tuesday Community Events Day</track><persons /></event></room><room name="Beta 2"><event id="7150"><start>09:00</start><duration>03:30</duration><room>Beta 2</room><title>PostgreSQL on Kubernetes Summit</title><abstract>&lt;p class="centred"&gt;
  A half-day event focused on running PostgreSQL in cloud native (and cloud neutral) environments. We'll explore the current landscape of Postgres operators (like CloudNativePG, Crunchy, Zalando, etc.), share best practices, discuss challenges, and go deeper into production stories from both users and maintainers.
&lt;/p&gt;

&lt;p&gt;
  Attendees will gain practical insight into the tradeoffs of different operators, backup and recovery in K8s, scaling strategies, monitoring, and zero-downtime upgrades. The format will include short talks, roundtable discussions, and panel Q&amp;As to maximize participation and knowledge sharing.
&lt;/p&gt;

&lt;p&gt;
If you're running Postgres on Kubernetes today, building an operator, or just interested in learning more, this event will help you navigate the fast-evolving world of databases on K8s.
&lt;/p&gt;

&lt;p&gt;
  Key Themes &amp; Benefits for the Community:
  &lt;ul&gt;
    &lt;li&gt;Comparative operator design discussions (Zalando, CloudNativePG, Crunchy, etc.)&lt;/li&gt;
    &lt;li&gt;Cross-vendor collaboration and open exchange of lessons learned&lt;/li&gt;
    &lt;li&gt;Operator internals: failover handling, PVCs, auto-scaling, backups&lt;/li&gt;
    &lt;li&gt;Use cases: Multi-tenant DBaaS platforms, CI/CD pipelines, GitOps&lt;/li&gt;
    &lt;li&gt;Roadmap alignment and interoperability&lt;/li&gt;
  &lt;/ul&gt;
&lt;/p&gt;

&lt;nav class="button-bar"&gt;
    &lt;a class="button primary" href="https://2025.pgconf.eu/community-events/postgresql-on-kubernetes-summit/"&gt;Find Out More&lt;/a&gt;
&lt;/nav&gt;</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7150/</url><track>Tuesday Community Events Day</track><persons /></event></room><room name="Gamma"><event id="7148"><start>09:00</start><duration>03:30</duration><room>Gamma</room><title>Extensions Showcase</title><abstract>&lt;p class="centred"&gt;
  One of the great things about Postgres is its extensibility and the range of interesting extensions available. With all that variety, how do you find one that meets your particular needs, let alone get a picture of the entire ecosystem?
&lt;/p&gt;

&lt;p class="centred"&gt;
  Join us for a whistlestop tour of who is extending Postgres, and in what direction.
&lt;/p&gt;

&lt;p&gt;
Hear from creators and power users of Postgres extensions.
&lt;/p&gt;

&lt;p&gt;
  &lt;ul&gt;
    &lt;li&gt;What does the extension do?&lt;/li&gt;
    &lt;li&gt;Who builds and maintains it?&lt;/li&gt;
    &lt;li&gt;Where can you get it from?&lt;/li&gt;
&lt;/p&gt;

&lt;nav class="button-bar"&gt;
    &lt;a class="button primary" href="https://2025.pgconf.eu/community-events/extensions-showcase/"&gt;Find Out More&lt;/a&gt;
&lt;/nav&gt;</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7148/</url><track>Tuesday Community Events Day</track><persons /></event></room><room name="Lambda"><event id="7152"><start>09:00</start><duration>03:30</duration><room>Lambda</room><title>Establishing the PostgreSQL standard: What's Postgres compatible?</title><abstract>&lt;p class="centred"&gt;
  What does it mean to be "PostgreSQL compatible"? As PostgreSQL becomes "the new Linux" for the enterprise, this question becomes increasingly important. This half-day session invites Postgres developers, contributors, and community members to define a practical framework of criteria and tests for PostgreSQL compatibility.
&lt;/p&gt;

&lt;p&gt;
  &lt;strong&gt;About&lt;/strong&gt;
&lt;/p&gt;

&lt;p&gt;
  As PostgreSQL's success grows, so do the challenges of brand dilution and feature fragmentation from "Postgres-compatible" derivatives. This session will focus on designing a test harness using existing regression tests and propose new tests covering core features, build behaviour, Application Binary Interface (ABI) stabilit, and backup/replication. The goal is to outline a concrete path towards meaningful compatibility certification.
&lt;/p&gt;

&lt;p&gt;
  This will be a focused, technical working session.
&lt;/p&gt;

&lt;p&gt;
  &lt;strong&gt;Agenda&lt;/strong&gt;
  &lt;ul&gt;
    &lt;li&gt;Introduction &amp; Motivation: A brief overview of the current landscape and the goals of the session.&lt;/li&gt;
    &lt;li&gt;Group Discussions: Participants will split into small groups, with discussion leads for each topic, to identify compatibility concerns and propose test approaches.&lt;/li&gt;
    &lt;li&gt;Presentations &amp; Roadmap: Each group will present their findings, followed by a collaborative session to outline a preliminary roadmap.&lt;/li&gt;
  &lt;/ul&gt;
&lt;/p&gt;

&lt;p&gt;
  &lt;strong&gt;Interest areas&lt;/strong&gt;
  &lt;ul&gt;
    &lt;li&gt;SQL Features &amp; Core Behaviour: What defines the essential PostgreSQL user experience?&lt;/li&gt;
    &lt;li&gt;Test Coverage: Build tests, behavioural tests, and ABI stability.&lt;/li&gt;
    &lt;li&gt;Backup &amp; Replication: Ensuring compatibility with standard tools and protocols (WAL, PITR, streaming, logical)&lt;/li&gt;
    &lt;li&gt;Identity: If a product is compatible but not the C (vanilla) implementation, is it still PostgreSQL?&lt;/li&gt;
  &lt;/ul&gt;
&lt;/p&gt;

&lt;p&gt;
We aim to close the session with a preliminary outline of criteria for meaningful compatibility testing and a roadmap for continued collaboration.
&lt;/p&gt;

&lt;nav class="button-bar"&gt;
    &lt;a class="button primary" href="https://2025.pgconf.eu/community-events/establishing-the-postgresql-standard-whats-postgres-compatible/"&gt;Find Out More&lt;/a&gt;
&lt;/nav&gt;</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7152/</url><track>Tuesday Community Events Day</track><persons /></event></room><room name="Ksi"><event id="7157"><start>09:00</start><duration>03:30</duration><room>Ksi</room><title>Crafty Slonik - Morning Session</title><abstract>&lt;p class="centred"&gt;
  Crafty Slonik is the event for people in the PostgreSQL community to showcase their hobbies outside of PostgreSQL. This event is about hacking, crafting and making all manner of things, except there will strictly be no hacking of PostgreSQL code!
&lt;/p&gt;

&lt;div class="card"&gt;
&lt;p&gt;
  Crafty Slonik is going to be hands on and interactive. It'll be a fun space for you to share your craft, to try something else, or try something totally new.  Come and hand out all day with others from the community or drop in and out as you need.  Most importantly relax and have a little fun being creative.  We'll provide a range of materials and implements (with in the limits of the venue), so therre is nothing to keep you away.
&lt;/p&gt;

&lt;p&gt;
  We intend this event to have a range of activities:
  &lt;ul&gt;
    &lt;li&gt;Cross stitch, knitting &amp; Crochet&lt;/li&gt;
    &lt;li&gt;Drawing, illustration, doodling&lt;/li&gt;
    &lt;li&gt;Quilling &amp; other paper craft&lt;/li&gt;
    &lt;li&gt;LED badges &amp; electronic arts&lt;/li&gt;
  &lt;/ul&gt;
&lt;/p&gt;
&lt;/div&gt;

&lt;div class="card"&gt;
&lt;h4&gt;The Great Community Slonik&lt;/h4&gt;

&lt;p&gt;
  The aim is for everyone to show of their creative flare and contribute to a mosaic: The Great Community Slonik.  Where we'll create a patchwork elephant to show a different side to our community, one of passion, skill and creativity.
&lt;/p&gt;

&lt;p&gt;
  People can produce one or more patches, using the various crafts we can do on-site.  Which will be photographed and added to The Great Community Slonik.  So you still get to keep what you made.
&lt;/p&gt;

&lt;p&gt;
  Anyone attending the Community Day can drop in and create a patch, o better a time to try something new out.  We'll have some guides and templates to make it easy for begineers to pros.
&lt;/p&gt;

&lt;h6&gt;Can't Make It On The Day&lt;/h6&gt;

&lt;p&gt;Don't worry if you can't make PGConf.EU 2025 or the community day event.  The hope is for the art work to live (and grow) online.  So you should be able to send us a patch remotely.&lt;/p&gt;
&lt;/div&gt;

&lt;div class="card"&gt;
&lt;h4&gt;How It'll work&lt;/h4&gt;

&lt;p&gt;
  On the day, we'll have a room dedicated to Crafty Slonik all day.  We'll have round tables geared up to the different crafts we can do.  You can get to know other members of the community with similar crafts.
&lt;/p&gt;

&lt;p&gt;
  Come along and contribute to our community art work or feel free to come and work on your own thing.  Crafty Slonik is an open and welcoming space of all.
&lt;/p&gt;

&lt;p&gt;
  Fundamentally this is a collaborative and interactive session.  It'll be as good as we all make it.
&lt;/p&gt;
&lt;/div&gt;

&lt;nav class="button-bar"&gt;
    &lt;a class="button primary" href="https://2025.pgconf.eu/community-events/crafty-slonik/"&gt;Find Out More&lt;/a&gt;
&lt;/nav&gt;</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7157/</url><track>Tuesday Community Events Day</track><persons /></event></room><room name="Other"><event id="7243"><start>12:30</start><duration>01:00</duration><room>Other</room><title>Lunch</title><abstract /><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7243/</url><track>Breaks</track><persons /></event></room><room name="Beta 1"><event id="7151"><start>13:30</start><duration>03:30</duration><room>Beta 1</room><title>Community Organizers Conf</title><abstract>&lt;h5 class="centred"&gt;A mini-conference for conference organizers? Heck yeah!&lt;/h5&gt;

&lt;p class="centred"&gt;
  Come and share how you made your events a success, share what didn't work for you, share the ideas that you want to try.
&lt;/p&gt;

&lt;/p&gt;
  A mini-conference for conference organizers? Heck yeah! Calling all Postgres (community) events, and meetup organizers to spend half a day discussing tips &amp; tricks, lessons learned, and ideas for future events.
&lt;/p&gt;

&lt;nav class="button-bar"&gt;
    &lt;a class="button primary" href="https://2025.pgconf.eu/community-events/community-organizers-conf/"&gt;Find Out More&lt;/a&gt;
&lt;/nav&gt;</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7151/</url><track>Tuesday Community Events Day</track><persons /></event></room><room name="Beta 2"><event id="7149"><start>13:30</start><duration>03:30</duration><room>Beta 2</room><title>PostgreSQL &amp; AI Summit</title><abstract>&lt;p class="centred"&gt;
  Explore the dynamic intersection of PostgreSQL and artificial intelligence! This half-day event brings together developers, engineers, data scientists, and AI enthusiasts to share experiences and insights on building AI-powered applications with PostgreSQL.
&lt;/p&gt;

&lt;p&gt;
  Topics may include vector search (pgvector) and hybrid search, PostgreSQL as context and tool provider for agentic AI, conversational access to PostgreSQL, tuning PostgreSQL with machine learning, integration strategies, and best practices for AI solution architectures with PostgreSQL. Featuring talks, panel discussions, demos, and plenty of time for open discussions, this collaborative event invites the PostgreSQL community to explore advancements in the AI space and to discuss how PostgreSQL for AI and AI for PostgreSQL are shaping the future of databases and artificial intelligence.
&lt;/p&gt;

&lt;nav class="button-bar"&gt;
    &lt;a class="button primary" href="https://2025.pgconf.eu/community-events/postgresql-and-ai-summit/"&gt;Find Out More&lt;/a&gt;
&lt;/nav&gt;</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7149/</url><track>Tuesday Community Events Day</track><persons /></event></room><room name="Gamma"><event id="7153"><start>13:30</start><duration>03:30</duration><room>Gamma</room><title>Patroni community summit</title><abstract>&lt;p class="centred"&gt;
  This half-day session is for developers, contributors, and users of Patroni who want to discuss current work, share ideas, and coordinate future development.
&lt;/p&gt;

&lt;p&gt;
  Several people and companies are working on different features, and this summit is a chance to talk about them in person. The format will be informal and interactive, with short talks, open discussions, and time for smaller group conversations. Topics will include new features, integration with PostgreSQL tools, deployment challenges, and ideas for improving Patroni. The goal is to help maintainers, contributors and users stay aligned, avoid duplicated effort, and make it easier to collaborate. Anyone involved with Patroni is welcome to join.
&lt;/p&gt;

&lt;nav class="button-bar"&gt;
    &lt;a class="button primary" href="https://2025.pgconf.eu/community-events/patroni-community-summit/"&gt;Find Out More&lt;/a&gt;
&lt;/nav&gt;</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7153/</url><track>Tuesday Community Events Day</track><persons /></event></room><room name="Lambda"><event id="7155"><start>13:30</start><duration>03:30</duration><room>Lambda</room><title>Conference Code of Conduct Management &amp; Volunteer Training</title><abstract>&lt;h4&gt;Conference Code of Conduct Management&lt;/h4&gt;
&lt;p class="centred"&gt;
  One of the requirements for community recognition of a conference is that the conference “adopt and follow an appropriate Code of Conduct to ensure a safe and enjoyable environment for anyone who wishes to attend.” That’s easy, if you have done it before.
&lt;/p&gt;

&lt;p&gt;
  But what if you haven’t done one before? You need to decide whether to use an existing CoC, such as the PostgreSQL Community Code of Conduct, or create one. You need to decide who is going to be on the CoC Committee, how they will respond to incident reports, and what to do if the complaint involves a member of the conference organization team—or, worse, yet, a member of the Conference Code of Conduct Committee.
&lt;/p&gt;

&lt;p&gt;
  We’ll work through the entire process, with time for Q&amp;A along the way. You’ll leave with a step-by-step plan, template documents, and a clear idea of what to do—and what *not* to do.
&lt;/p&gt;

&lt;p&gt;
  As the creator of the original PostgreSQL Community Code of Conduct, and the Committee Chair for the initial three year term, I have experience in building both a CoC policy and a CoC Committee from scratch. I have also managed the Code of Conduct Committee for PgConf.EU from 2023 to present, and for PgConf.Dev in 2025.
&lt;/p&gt;

&lt;nav class="button-bar"&gt;
    &lt;a class="button primary" href="https://2025.pgconf.eu/community-events/conference-code-of-conduct-management/"&gt;Find Out More&lt;/a&gt;
&lt;/nav&gt;

&lt;h4&gt;Volunteer Training&lt;/h4&gt;
&lt;p class="centred"&gt;
  Conferences rely heavily on volunteer staff, most of whom are good at their jobs and want to do the right thing. That’s a great start, but it’s not enough. When you have 800 people from all over the world in one place, speaking multiple languages, and operating from different cultural frames, things happen, not all of them good.
&lt;/p&gt;

&lt;p&gt;
  An attendee may have special needs that no one knows how to accommodate. Another attendee may become agitated over an apparent small incident, or an attendee drinks too much at the social. An attendee may have unexpected situation to deal with on the spot (for example, receiving bad news in the break between sessions) that results in an emotional outburst next to the coffee station. 
&lt;/p&gt;

&lt;p&gt;
  We’ll combine discussion and role playing (everyone gets a chance to be on stage if they wish!) to practice active listening, recognizing hidden bias, identifying underlying issues, finding workable solutions, and de-escalating conflicts.
&lt;/p&gt;

&lt;nav class="button-bar"&gt;
    &lt;a class="button primary" href="https://2025.pgconf.eu/community-events/volunteer-training/"&gt;Find Out More&lt;/a&gt;
&lt;/nav&gt;</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7155/</url><track>Tuesday Community Events Day</track><persons /></event></room><room name="Ksi"><event id="7156"><start>13:30</start><duration>03:30</duration><room>Ksi</room><title>Crafty Slonik - Afternoon Session</title><abstract>&lt;p class="centred"&gt;
  Crafty Slonik is the event for people in the PostgreSQL community to showcase their hobbies outside of PostgreSQL. This event is about hacking, crafting and making all manner of things, except there will strictly be no hacking of PostgreSQL code!
&lt;/p&gt;

&lt;div class="card"&gt;
&lt;p&gt;
  Crafty Slonik is going to be hands on and interactive. It'll be a fun space for you to share your craft, to try something else, or try something totally new.  Come and hand out all day with others from the community or drop in and out as you need.  Most importantly relax and have a little fun being creative.  We'll provide a range of materials and implements (with in the limits of the venue), so therre is nothing to keep you away.
&lt;/p&gt;

&lt;p&gt;
  We intend this event to have a range of activities:
  &lt;ul&gt;
    &lt;li&gt;Cross stitch, knitting &amp; Crochet&lt;/li&gt;
    &lt;li&gt;Drawing, illustration, doodling&lt;/li&gt;
    &lt;li&gt;Quilling &amp; other paper craft&lt;/li&gt;
    &lt;li&gt;LED badges &amp; electronic arts&lt;/li&gt;
  &lt;/ul&gt;
&lt;/p&gt;
&lt;/div&gt;

&lt;div class="card"&gt;
&lt;h4&gt;The Great Community Slonik&lt;/h4&gt;

&lt;p&gt;
  The aim is for everyone to show of their creative flare and contribute to a mosaic: The Great Community Slonik.  Where we'll create a patchwork elephant to show a different side to our community, one of passion, skill and creativity.
&lt;/p&gt;

&lt;p&gt;
  People can produce one or more patches, using the various crafts we can do on-site.  Which will be photographed and added to The Great Community Slonik.  So you still get to keep what you made.
&lt;/p&gt;

&lt;p&gt;
  Anyone attending the Community Day can drop in and create a patch, o better a time to try something new out.  We'll have some guides and templates to make it easy for begineers to pros.
&lt;/p&gt;

&lt;h6&gt;Can't Make It On The Day&lt;/h6&gt;

&lt;p&gt;Don't worry if you can't make PGConf.EU 2025 or the community day event.  The hope is for the art work to live (and grow) online.  So you should be able to send us a patch remotely.&lt;/p&gt;
&lt;/div&gt;

&lt;div class="card"&gt;
&lt;h4&gt;How It'll work&lt;/h4&gt;

&lt;p&gt;
  On the day, we'll have a room dedicated to Crafty Slonik all day.  We'll have round tables geared up to the different crafts we can do.  You can get to know other members of the community with similar crafts.
&lt;/p&gt;

&lt;p&gt;
  Come along and contribute to our community art work or feel free to come and work on your own thing.  Crafty Slonik is an open and welcoming space of all.
&lt;/p&gt;

&lt;p&gt;
  Fundamentally this is a collaborative and interactive session.  It'll be as good as we all make it.
&lt;/p&gt;
&lt;/div&gt;

&lt;nav class="button-bar"&gt;
    &lt;a class="button primary" href="https://2025.pgconf.eu/community-events/crafty-slonik/"&gt;Find Out More&lt;/a&gt;
&lt;/nav&gt;</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7156/</url><track>Tuesday Community Events Day</track><persons /></event></room></day><day date="2025-10-22"><room name="Other"><event id="7170"><start>08:30</start><duration>01:00</duration><room>Other</room><title>Registration</title><abstract /><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7170/</url><track>PGConf.EU</track><persons /></event></room><room name="Omega 1"><event id="7168"><start>09:30</start><duration>00:15</duration><room>Omega 1</room><title>Welcome and Opening</title><abstract /><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7168/</url><track>PGConf.EU</track><persons><person id="1">Magnus Hagander</person></persons></event><event id="7176"><start>09:45</start><duration>01:00</duration><room>Omega 1</room><title>The Foundation of Open Source: Why Software Freedom?</title><abstract>Open source has become the backbone of society's software. Critical
projects like PostgreSQL power some of the most important software in
the industry. While many aspects of Open Source make software
successful, such as its collaborative development model and price, these
features are all underpinned and guaranteed by the software freedom that
Open Source licenses provide. In this talk, Karen will explore why
software freedom is essential to modern day computing, as well as to
every day life.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7176/</url><track>Keynotes</track><persons><person id="1420">Karen Sandler</person></persons></event></room><room name="Other"><event id="7158"><start>10:45</start><duration>00:30</duration><room>Other</room><title>Coffee Break</title><abstract /><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7158/</url><track>Breaks</track><persons /></event></room><room name="Omega 1"><event id="6838"><start>11:15</start><duration>00:50</duration><room>Omega 1</room><title>Don't do that!</title><abstract>Rather than presenting best practices, I'll show a number of design choices that have repeatedly caused problems for users. Learn from the errors of others!

Topics include:
- choosing the wrong data type
- choosing "integer" as data type for primary keys
- defining columns nullable
- using Large Objects
- defining dangerous CHECK constraints
- lying about IMMUTABLE
- choosing an entity-attribute-value design</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/6838/</url><track>App Developer (45 minutes)</track><persons><person id="191">Laurenz Albe</person></persons></event></room><room name="Omega 2"><event id="7138"><start>11:15</start><duration>00:50</duration><room>Omega 2</room><title>From Stars to Storage Engines: Migrating Big Science Workloads Beyond Greenplum</title><abstract>We archive massive datasets to map the stars in ESA’s Gaia mission and unlock the secrets of dark matter and dark energy with Euclid. Today, these are living on Greenplum — but shifting away from Open Source Software demands have us exploring new directions: migrating to Citus or adopting EDB’s next-generation Greenplum-based warehouse.

In this talk, we’ll share how we’re rethinking architecture, tools, and operations to handle petabyte-scale astronomy workloads. We’ll cover the practical pros and cons of each option, the administrative shifts required, and the hurdles we face moving such critical operations between engines. Attendees will leave with real-world lessons and key questions to ask before starting a migration of their own.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7138/</url><track>DBA (45 minutes)</track><persons><person id="1356">Joaquim Oliveira</person></persons></event></room><room name="Alfa"><event id="6935"><start>11:15</start><duration>00:50</duration><room>Alfa</room><title>Behind Postgres 18: The People, the Code, &amp; the Invisible Work</title><abstract>Ever wonder who makes Postgres happen? Not just the new features in Postgres 18—but the people, the processes, and the invisible work that brings each new release to life? Let’s find out. In an open source project like Postgres, recognizing the behind-the-scenes volunteer work isn’t just nice—it’s necessary.  

This revamped version of last year’s PGConf EU talk shares a fresh analysis of the contributions to Postgres in the v18 timeframe. Like last year’s talk, this research is done by Postgres committer Daniel Gustafsson and Claire Giordano—and builds on community data sources including commit logs, mailing lists, and the PostgreSQL.org site. You’ll see maps and charts as you learn about the people behind governance, conferences, meetups, infrastructure, and the code. But this year there will be new insights—and more stories. Like: who translates all the error messages? And what went into making PGConf.dev feel so magical? 

You’ll leave with a deeper appreciation for the full spectrum of work behind a Postgres release—and a few concrete ideas for how we can better recognize the people who make it happen. Because when we recognize the people doing this work, it’s more than a thank you—it’s how we grow the next generation of contributors.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/6935/</url><track>Community (45 minutes)</track><persons><person id="535">Claire Giordano</person></persons></event></room><room name="Beta"><event id="7177"><start>11:15</start><duration>00:50</duration><room>Beta</room><title>From Transactions to Intelligence: Postgres for Open AI &amp; Analytics</title><abstract>Postgres has thrived for decades as the world’s most trusted open-source database, powering an extraordinary share of transactional workloads across industries. But the data landscape is shifting: analytics and AI demand far richer data modalities, more diverse programming models, and new ways of consuming data. To meet this future, Postgres must not only endure — it must evolve.
In this talk, we’ll explore three powerful pathways driving that evolution. First, the organic path, where Postgres itself grows new capabilities — think WarehousePG for analytics or pgvector and friends for AI. Second, the hybrid path, where Postgres joins forces with other open-source engines like DataFusion and open metadata frameworks such as Iceberg REST catalogs. And third, the augmented path, where Postgres extends into entirely new ecosystems — becoming a first-class citizen in agentic AI through robust MCP-driven tooling.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7177/</url><track>Sponsors</track><persons><person id="1400">Torsten Steinbach</person></persons></event></room><room name="Other"><event id="7164"><start>12:05</start><duration>01:00</duration><room>Other</room><title>Lunch</title><abstract /><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7164/</url><track>Breaks</track><persons /></event></room><room name="Omega 1"><event id="7067"><start>13:05</start><duration>00:30</duration><room>Omega 1</room><title>Anonymizing Data in Postgres Without Losing Your Mind (or Your Schema)</title><abstract>Scrubbing sensitive data in PostgreSQL can feel like a chore, especially when you're trying to do it safely, flexibly, and without rewriting your entire schema. Many teams face the need for column-level anonymization when working with production clones, analytics pipelines, or complying with regulations like GDPR. Doing it well can be a real challenge.

In this talk, we’ll walk through modern, practical ways to anonymize data in Postgres. We’ll cover how to mask or hash specific columns, handle nested fields (like JSON), and even apply different rules based on data values, all without touching the original database structure. You’ll see examples of redaction, pseudonymization, and other transformations that keep your data useful while protecting what matters. We’ll also compare popular open-source tools like pg_anonymize, known for in-database anonymization, with platforms like Greenmask and NeoSync that focus on masking and secure data syncing. Some of these tools are integrated directly into pgstream, enabling seamless, real-time data transformations as part of logical replication workflows.

To bring it all together, we’ll look at how pgstream, an open-source tool that uses logical replication and supports plug-and-play data transformers, can help apply these anonymization techniques in real time. pgstream integrates with several of the open-source tools mentioned earlier, allowing you to set up custom or built-in anonymization rules with simple configuration and without requiring major changes to your database.

If you’ve ever needed to clean up sensitive data before sending it downstream (or just wanted a cleaner way to do it), this talk will give you the tools and ideas to make it happen.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7067/</url><track>App Developer (25 minutes)</track><persons><person id="1365">Ahmet Gedemenli</person><person id="1157">Esther Miñano Sanz</person></persons></event></room><room name="Omega 2"><event id="6975"><start>13:05</start><duration>00:30</duration><room>Omega 2</room><title>Parsing Postgres logs the non-pgBadger way</title><abstract>pgBadger has been a staple in the community for over a decade, and deserves a nod for sure. But at the same time one also has to acknowledge that the world has changed a "bit" during that time.

Are there some log parsing use cases that are better served with something else? What are the current options besides ad-hoc grep?

This talk is a look at a fresh effort to provide an alternative Open Source log parser to complement pgBadger.

We'll look at how pgweasel tries to be:

- way faster
- way simpler - concentrating on the Pareto DBA flow and the CLI experience
- more cloud-friendly
- require zero configuration
- more user-friendly</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/6975/</url><track>DBA (25 minutes)</track><persons><person id="337">Kaarel Moppel</person></persons></event></room><room name="Alfa"><event id="7009"><start>13:05</start><duration>00:30</duration><room>Alfa</room><title>Data modeling with PostgreSQL at the core of Software Development</title><abstract>Data structures and their relationships are key to software design. For most, how data is organized is even more important than the application code itself, because the code, the flowcharts and the processes will be derived and become straightforward from the data structure and their relationships. Learning how to model your data and how to design your schema in PostgreSQL becomes fundamental to create a successful software project. How would you store and organize the data? Which data types would you use? Will there be any constraints? And most importantly, which types of questions will your application be able to answer directly from the data?

Honoring Mikhail Tal, the Magician from Riga, eighth World Chess Champion, in this talk we will go through the design of an application to track the results of a chess tournament. You will learn some principles of data modeling, letting PostgreSQL guarantee data integrity. We will see how to build the business logic of the application in the data model itself, giving you extra powers as a software developer.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7009/</url><track>App Developer (25 minutes)</track><persons><person id="541">Boriss Mejias</person></persons></event></room><room name="Omega 1"><event id="7008"><start>13:45</start><duration>00:50</duration><room>Omega 1</room><title>Boosting Typical Query Patterns: PostgreSQL 18's Performance Enhancements</title><abstract>As with previous releases, PostgreSQL 18 introduces many performance improvements that directly benefit everyday database tasks. 

Beyond doing an overview of the performance improvements, this talk will go over these changes and compare the performance of popular applications using PostgreSQL 16, 17 and 18, to highlight the improvements in PG 18.

The optimizer now automatically eliminates unnecessary self-joins, converts IN (VALUES ...) to x = ANY ... for better statistics, and transforms OR-clauses into arrays for faster index processing. It also speeds up INTERSECT, EXCEPT, window aggregates, and optimizes SELECT DISTINCT and GROUP BY queries by reordering keys and ignoring redundant columns.

This talk will walk through these and many more, while showing data from running applications.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7008/</url><track>App Developer (45 minutes)</track><persons><person id="778">Roberto Mello</person></persons></event></room><room name="Omega 2"><event id="6982"><start>13:45</start><duration>00:50</duration><room>Omega 2</room><title>Vector data in Postgres: Size, TOAST, Filters and Performance</title><abstract>AI applications are changing how we use databases, and vector data is at the center of this change.  By enabling semantic search within domain datasets, vectors allow for more intelligent and nuanced queries. But managing this data effectively requires understanding the challenges of vector size and its impact on storage and performance. This presentation explores practical strategies for storing, indexing, and querying vector data in operational databases and different factors impacting performance and management.  Learn how to optimize your database for AI-powered applications and unlock the full potential of vector search.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/6982/</url><track>DBA (45 minutes)</track><persons><person id="1005">Gleb Otochkin</person></persons></event></room><room name="Alfa"><event id="6952"><start>13:45</start><duration>00:50</duration><room>Alfa</room><title>Improved Freezing in Postgres Vacuum: From Idea to Commit</title><abstract>This talk uses the recently committed eager scanning feature as a case study to walk through the Postgres feature development process. It’s meant to give prospective contributors a realistic look at what it takes to get a feature committed and to help users better understand how Postgres evolves and how they can benefit from these changes.

Anti-wraparound vacuums are one of the most consistent Postgres user complaints. This talk explains how freeze debt accumulates, how it varies based on table access patterns, and how Postgres attempts to manage it.

Eager scanning started as a proposal on pgsql-hackers to preemptively freeze modified pages using per-table access pattern statistics.

Over years of discussion and experimentation (including evaluating and discarding many empirical models and approaches), the shape of both the problem and solutions evolved. This talk dives into what made designing an adaptive feature in Postgres so difficult: extreme constraints, second-order effects, code complexity, and the sheer variety of workloads Postgres must support.

The final committed feature is simpler than the original idea: it eagerly scans all-visible but not all-frozen pages to amortize the cost of aggressive vacuums. It doesn’t try to predict access patterns or freeze lifespan, but it’s effective, maintainable, and is a step toward addressing the core problem.

Finally, the talk will explain how users can expect this change to reduce the frequency and impact of anti-wraparound vacuums in their own workloads.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/6952/</url><track>Postgres Internals (45 minutes)</track><persons><person id="993">Melanie Plageman</person></persons></event></room><room name="Beta"><event id="7180"><start>13:45</start><duration>00:50</duration><room>Beta</room><title>What we built with Open Source</title><abstract>After more than 25 years working with PostgreSQL, we’ve seen it all, from clever hacks to some of the most ambitious deployments out there.

PostgreSQL’s rich ecosystem makes it possible to cover just about every need, including monitoring, tuning, automation, compliance, scalability, and high availability.

In this talk, we’ll take you behind the scenes and show you what we’ve built along the way: open-source contributions, customer solutions, and custom projects designed to solve real-world problems. Join us for a tour of cool ideas, battle-tested tools, and lessons learned from the field.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7180/</url><track>Sponsors</track><persons><person id="1404">Hans-Jürgen Schönig</person></persons></event></room><room name="Omega 1"><event id="6800"><start>14:45</start><duration>00:50</duration><room>Omega 1</room><title>Practical Guide to Migrating +100 Large PostgreSQL to the Cloud</title><abstract>Migrating a large fleet of PostgreSQL databases to a managed service is a journey filled with opportunities and potential pitfalls. This is especially true when dealing with numerous multi-terabyte databases and particular cases such as migrating from an old version, using inheritance, PostGIS, moving to GCP Service accounts, and changing database assignment to instances.
This session shares the real-world experience of migrating more than 100 PostgreSQL databases, ranging in size from gigabytes to multiple terabytes, from traditional virtual machines to a managed cloud service, specifically Google Cloud SQL for PostgreSQL. 

We will share lessons learned, covering planning, execution, and problems encountered, with practical advice to save you time, resources, and headaches during a similar migration.  Key discussion areas will include tooling selection, pre-migration assessments, choosing the right instance type, optimizing the migration process for large datasets, strategies for minimizing downtime, and essential post-migration validation and performance tuning. 

This session is a must-attend for anyone considering or currently executing a large-scale PostgreSQL migration to a managed service and wants to learn from real-world successes and challenges.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/6800/</url><track>DBA (45 minutes)</track><persons><person id="948">Nelson Calero</person></persons></event></room><room name="Omega 2"><event id="6817"><start>14:45</start><duration>00:50</duration><room>Omega 2</room><title>Operational hazards of managing PostgreSQL DBs over 100TB</title><abstract>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...

And you start questioning yourself: how do you backup (and restore) a +100TB database? And how about HA? Performance? Vacuum?

It should work the same way as for a 100GB database, right? Well, maybe not exactly.

Blog posts and best practice guides make PostgreSQL seem straightforward—until you push it to its limits. At extreme scale, you will find yourself questioning the most fundamental assumptions about how PostgreSQL works.

Over the last years, my team at Adyen has been exploring the boundaries of what PostgreSQL can do, and today I will share our findings with you (at least the ones I can!).</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/6817/</url><track>DBA (45 minutes)</track><persons><person id="1130">Teresa Lopes</person></persons></event></room><room name="Alfa"><event id="7103"><start>14:45</start><duration>00:50</duration><room>Alfa</room><title>Barman, past, present, and future of a pioneer community project</title><abstract>Barman is one of the first Backup and Recovery management tool for Postgres, released as an open-source tool by 2ndQuadrant, with lots of adopters in the last decade.

In this talk, we will go over the history of Barman as a community project, from its beginning to the current state of affairs. We will be showing the great achievements, the pain-point moments, and the future.

We hope to: 
* Enlighten people with Backup and Recovery insights (yes, we will talk about Backups)
* Share how the teams have interacted with the community, balancing the customer requests with community proposals
* Go over these 13 years of open source development 
* Describe where we plan to take the project in the future, in terms of development features, and engagement with the community

We hope to leave an itch to either join our community or start your own community project, preferably in the Postgres ecosystem.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7103/</url><track>Community (45 minutes)</track><persons><person id="367">Giulio Calacoci</person><person id="200">Martín Marqués</person></persons></event></room><room name="Beta"><event id="7184"><start>14:45</start><duration>00:50</duration><room>Beta</room><title>Unlock PostgreSQL’s True Performance with Local SSDs</title><abstract>Cloud storage was built around the limits of old hardware. Spinning hard drives (HDDs) were slow and fragile. So, early on, cloud providers moved storage off of servers. They used network-attached disks to boost durability and scalability. But hardware has evolved. Today, you can get 2.5 million IOPS from a $600 NVMe SSD. Achieving the same throughput through network-attached storage in the cloud can cost hundreds of thousands of dollars per month. With NVMe SSDs now faster, cheaper, and more reliable, it's time to rethink PostgreSQL storage.

In this talk, we’ll walk through different disk architectures and their impacts on PostgreSQL performance, how we got here, what’s changed, and why local NVMe SSDs are the future for PostgreSQL storage. We'll also share benchmarks comparing performance on different disk architectures and share results from real life case studies.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7184/</url><track>Sponsors</track><persons><person id="1408">Burak Yucesoy</person></persons></event></room><room name="Other"><event id="7159"><start>15:35</start><duration>00:30</duration><room>Other</room><title>Coffee Break</title><abstract /><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7159/</url><track>Breaks</track><persons /></event></room><room name="Omega 1"><event id="6868"><start>16:05</start><duration>00:50</duration><room>Omega 1</room><title>Normalize or De-normalize? Relational SQL Columns or JSON Document Attributes?</title><abstract>Data modeling has progressed beyond traditional SQL Normal Forms and the unstructured storage of early NoSQL systems. Modern applications demand flexible data models that merge normalized entities with semi-structured documents. Contemporary SQL databases now support binary JSON columns and offer APIs similar to MongoDB (such as FerretDB for PostgreSQL). Furthermore, NoSQL databases have evolved to allow normalized collections and provide transactional operations.

However, key questions remain: When should multiple entities be embedded within a single JSONB document? And when is it more efficient to define a relational column instead of a sub-document attribute?

This session will clarify the distinction between physical and logical data modeling. Denormalization can enhance physical storage by placing frequently accessed data together, while normalization is essential for maintaining logical data integrity and preventing issues related to redundancy. By the end of this session, you will understand how to balance these two approaches to create data models that are efficient, maintainable, and adaptable to changing application requirements.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/6868/</url><track>App Developer (45 minutes)</track><persons><person id="618">Franck Pachot</person></persons></event></room><room name="Omega 2"><event id="7133"><start>16:05</start><duration>00:50</duration><room>Omega 2</room><title>What You Should Know About Constraints in PostgreSQL (and What’s New in 18)</title><abstract>PostgreSQL 18 introduces significant enhancements to constraints, your first line of defense for maintaining data integrity. This talk focuses on the new capabilities brought by version 18, including non-overlapping PRIMARY KEY and UNIQUE constraints, named NOT NULL constraints, NOT ENFORCED constraints, and improved support for partitioned tables. We’ll look at what’s new, why it matters, and how to apply these features in real-world systems. 

We will begin with a brief refresher on the different types of constraints (CHECK, NOT NULL, UNIQUE, PRIMARY KEY, FOREIGN KEY) to help you get the most out of PostgreSQL’s declarative integrity model. Then we’ll go into details of what's new in PostgreSQL 18, including:
* Named NOT NULL constraints and their inclusion to foreign tables
* NOT ENFORCED constraints for CHECK and foreign keys
* WITHOUT OVERLAPS
* ALTER TABLE ... ALTER CONSTRAINT ... [NO] INHERIT
* Enhanced handling of constraints on partitioned tables
* Requirements around deterministic/nondeterministic collations in primary/foreign key relationships</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7133/</url><track>DBA (45 minutes)</track><persons><person id="1350">Gülçin Yıldırım Jelínek</person></persons></event></room><room name="Alfa"><event id="7056"><start>16:05</start><duration>00:50</duration><room>Alfa</room><title>What implementing pg_tde taught us about PostgreSQL</title><abstract>This is a firsthand account of bringing Transparent Data Encryption to PostgreSQL through pg_tde. From idea to patch proposals, it’s a story of navigating PostgreSQL’s internals, Community realities, and trade-offs between extension and core changes.
Why weren’t existing hooks enough? What friction did we hit? How was the experience with the Community feedback cycle? What customer feedback shaped the final design and how did users react to the proposed solutions? Based on years of work to deliver a critical enterprise capability, this talk is a diary of what it took to deliver Transparent Data Encryption as an extension to PostgreSQL, from a product manager who lived through it.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7056/</url><track>Community (45 minutes)</track><persons><person id="1232">Jan Wieremjewicz</person></persons></event></room><room name="Beta"><event id="7179"><start>16:05</start><duration>00:50</duration><room>Beta</room><title>DataGrip: A Powerful IDE for PostgreSQL</title><abstract>In this talk, Maxim Sobolevskiy is going to show what DataGrip is all about, from the basics to more complicated things like AI for SQL, databases in version control, and scripted mechanisms for data export.

What will be covered:
– Various types of IntelliSense, code snippets, expanding wildcards, and subqueries.
– AI Assistant: Text-to-SQL, Fix with AI, and AI-based export.
– Data editor: Editable result-sets, bulk and multiple submit, and transposing data.
– Data import/export: Import/export from CSV, JSON, Excel, and INSERT statements, and export to other databases.
– Navigation: Searching for database objects, data, SQL code, files, settings, and more.
– Additional tools: Diagrams, user-defined parameters, and a powerful diff tool.

DataGrip is built with one purpose in mind: to save developers from repetitive work. Join this session to find out how well it fulfills that purpose.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7179/</url><track>Sponsors</track><persons><person id="1402">Maxim Sobolevskiy</person></persons></event></room><room name="Omega 1"><event id="7046"><start>17:05</start><duration>00:50</duration><room>Omega 1</room><title>Hacking pgvector for performance</title><abstract>In this talk I will present a modification to the popular pgvector Postgres extension for approximate nearest neighbor search. The modified extension keeps the vector index persistent in external (Non-Postgres) memory, and pushes potential filter conditions directly into the index scan. Storage of index and compute can also be offloaded to a GPU. I will explain in detail the inner workings of a Postgres index scan, the rational behind moving core parts of pgvector away from Postgres, and the performance implications. I will also highlight how this modified extension finds application in massive data processing within the framework of the AERO project for the future heterogeneous EU cloud infrastructure.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7046/</url><track>App Developer (45 minutes)</track><persons><person id="1385">Daniel Krefl</person></persons></event></room><room name="Omega 2"><event id="6961"><start>17:05</start><duration>00:50</duration><room>Omega 2</room><title>Patroni and pgBackRest: better together</title><abstract>Even in a world of managed database services and cloud-native platforms, Patroni and pgBackRest remain two essential components in the PostgreSQL operations toolbox. This talk is your go-to guide for combining the strengths of this powerful duo to achieve high availability and disaster recovery.

You will learn how to integrate pgBackRest into a Patroni-managed cluster, safely rebuild standby nodes, bootstrap an entire cluster from an existing pgBackRest backup, and perform point-in-time recovery (PITR) entirely under Patroni's control.

Expect real-world examples, detailed YAML configuration snippets, and the kind of operational wisdom that only comes from lessons learned the hard way.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/6961/</url><track>DBA (45 minutes)</track><persons><person id="440">Stefan Fercot</person></persons></event></room><room name="Alfa"><event id="6989"><start>17:05</start><duration>00:50</duration><room>Alfa</room><title>All in a context!</title><abstract>Postgresql has a special way of handling memory management, which is via specialized data structure called memory context. All the memory allocation and deallocation are done using a memory context. One never requires independent calls to memory functions like free, malloc, etc. in PostgreSQL. Memory contexts are hierarchical in nature, so deleting a parent context deletes and deallocates all the children contexts, this eases the memory handling by avoiding memory leaks. There are also some specialised memory contexts defined like MessageContext, TopTransactionContext, PortalContext, ErrorContext with their specific purposes. There are APIs available to handle the working of memory contexts to create, delete, reallocate, deallocate, reset, or switch to other contexts. There are also APIs available to identify the current context or switch to some globally available memory contexts. This talk aims at discussing the details of memory management in PostgreSQL.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/6989/</url><track>Postgres Internals (25 minutes)</track><persons><person id="1098">Rafia Sabih</person></persons></event></room><room name="Beta"><event id="7181"><start>17:05</start><duration>00:50</duration><room>Beta</room><title>Exploring new enhancements and improvements Fujitsu has delivered to PostgreSQL</title><abstract>In this session we will dive into a series of recent contributions to PostgreSQL, made possible by the Fujitsu team working with sustained focus on core database features. 

We will explore some of these new enhancements and improvements including: 


1. Advanced Conflict Management

2. Parallel Apply for High Throughput

3. Table Exclusions

4. Seamless Cluster Upgrades

5. Slot Synchronization for High Availability</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7181/</url><track>Sponsors</track><persons><person id="1405">Vincent O'Dea</person></persons></event></room><room name="Other"><event id="7229"><start>18:00</start><duration>03:00</duration><room>Other</room><title>PostgreSQL Europe Reception</title><abstract>As with previous PGConf.EU events, the 2025 conference in Riga will have a social event.

Following the success of last year's event, we’re again making this year’s social easy for all to attend: just join us in the common area at the conclusion of the conference on Wednesday, October 22, for snacks, refreshments and activities. We look forward to seeing you and celebrating what we know will be a great conference!</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7229/</url><track>PGConf.EU</track><persons /></event></room></day><day date="2025-10-23"><room name="Other"><event id="7171"><start>08:30</start><duration>00:30</duration><room>Other</room><title>Registration</title><abstract /><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7171/</url><track>PGConf.EU</track><persons /></event></room><room name="Omega 1"><event id="7174"><start>09:00</start><duration>00:15</duration><room>Omega 1</room><title>Day 2 Welcome</title><abstract /><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7174/</url><track>PGConf.EU</track><persons><person id="323">Jimmy Angelakos</person></persons></event><event id="6960"><start>09:25</start><duration>00:50</duration><room>Omega 1</room><title>Have you ever wondered, how a cloud platform works?</title><abstract>Cloud Foundry is an open-source Platform as a Service project which is, that serves as the workhorse of the SAP Business Technology Platform, powered by PostgreSQL.

Database Performance is crucial for Cloud Foundry because it has direct effects to the performance and scalability of the installed platform which is crucial for its operations and high-demanding enterprise users.

Consequently, SAP contributes actively to optimizations of queries for PostgreSQL in Cloud Foundry to operate the Cloud Platform at a large scale. Over the years the Cloud Foundry team at SAP, gained experience in how to set up and run reliable and performant cloud foundry installations on AWS, Azure, Google Cloud and Alibaba Cloud. From outside the offerings looks similar, but you do not get similar offerings: This is especially a challenge in unified automation and monitoring of PostgreSQL databases on these infrastructures. 

Attendees will learn about  
- Cloud Foundry in general and the usage of PostgreSQL in this open-source project.  
- Running PostgreSQL on different cloud infrastructures -&gt; comparison of the different service offerings.  
- PostgreSQL optimizations for large scale cloud foundry installations in the code and in the database server. It is the foundation for some open-source contributions of SAP in this area.  
- Zero-downtime Schema Migrations in high load scenarios  
- Some true live stories about PostgreSQL major version upgrades which inexpertly caused problems.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/6960/</url><track>App Developer (45 minutes)</track><persons><person id="1369">Maximilian Stefanac</person><person id="1370">Philipp Thun</person></persons></event></room><room name="Omega 2"><event id="7035"><start>09:25</start><duration>00:50</duration><room>Omega 2</room><title>Unified Observability: Monitoring Postgres Anywhere with OpenTelemetry</title><abstract>PostgreSQL is widely used across cloud, Kubernetes, and bare metal environments. But how can we monitor it efficiently across all these setups without vendor lock-in or high costs? 

In this talk, we'll explore how OpenTelemetry helps achieve consistent and scalable observability for Postgres - no matter where it runs. We'll walk through how to collect metrics and logs, integrate them with open-source observability tools, and optimize monitoring for both performance and cost. 

Expect live demos and practical insights on making PostgreSQL monitoring simple, efficient, and future-ready with OpenTelemetry.

Key Takeaways:
- How OpenTelemetry brings consistent Postgres observability across cloud, kubernetes, and bare metal
- How to collect telemetry data (metrics and logs) for effective Postgres monitoring
- How to use open-source tools (Prometheus, Loki, Grafana) to observe Postgres
- Tips to reduce observability costs while keeping full visibility
- Live demo of Postgres monitoring in cloud-native environments</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7035/</url><track>DBA (45 minutes)</track><persons><person id="1381">Yogesh Jain</person></persons></event></room><room name="Alfa"><event id="6908"><start>09:25</start><duration>00:50</duration><room>Alfa</room><title>Why PostgreSQL people should really care about Kafka and Debezium?</title><abstract>In the realm of data management, the convergence of Postgres, Kafka, and Debezium heralds a new era of possibilities. 
This talk is a compelling exploration into why individuals immersed in the Postgres ecosystem must pay careful attention 
to Kafka and Debezium, unveiling the transformative impact of this trinity on data architecture.

The discussion kicks off by unraveling the unique strengths of each player - obviously Postgres as a robust relational database, 
Kafka as a resilient event streaming platform and Debezium as the linchpin enabling change data capture (CDC). 
Attendees will embark on a journey through the intricacies of integrating these technologies, understanding how their 
synergy facilitates real-time data propagation and synchronization.

Throughout the talk, we'll dive into the benefits that arise when Postgres enthusiasts embrace Kafka and Debezium, from 
unlocking unparalleled insights into database changes to fortifying data consistency across distributed systems. 
Practical insights and real-world examples will illuminate the potential pitfalls in this integration, coupled with 
strategies to navigate challenges effectively.

This talk aspires to empower Postgres aficionados to navigate the evolving data terrain with confidence, fostering a 
community that recognizes the symbiotic relationship between Postgres, Kafka, and Debezium as the key to unlocking the 
full potential of their data ecosystems.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/6908/</url><track>DBA (45 minutes)</track><persons><person id="718">Dirk Krautschick</person></persons></event></room><room name="Beta"><event id="7187"><start>09:25</start><duration>00:50</duration><room>Beta</room><title>DBtune: AI-driven performance tuning for all PostgreSQL flavors</title><abstract>Manual PostgreSQL tuning is an error prone guessing game resulting in volatile performance, costly over-provisioning, and unnecessary downtime. For enterprises managing large, heterogeneous database fleets, this problem is magnified, causing spiraling infrastructure costs and unpredictable behavior. This session introduces the new major release of the DBtune and address the challenge of tuning complex workloads for enterprises. Learn how DBtune's autonomous agent analyzes your unique workloads and adapts server parameters to maximize your database’s resource utilization and throughput. We will directly compare DBtune's adaptive approach to static methods like PGTune. Through a live demo, we will show you how DBtune operates seamlessly across any environment, from self-hosted community PostgreSQL to managed cloud services like Amazon RDS, Aurora, and Google Cloud SQL. You will discover practical strategies to automate tuning, achieve predictable high performance, and cost optimization.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7187/</url><track>Sponsors</track><persons><person id="1411">Dr. Luigi Nardi</person></persons></event></room><room name="Omega 1"><event id="6795"><start>10:25</start><duration>00:30</duration><room>Omega 1</room><title>EXPLAIN: make it make sense</title><abstract>Most developers know how to measure the time a database query takes and to find which one is the slowest. But what next? What is going on there? Is it good that it’s doing that? Is the query supposed to take this much time? Will some indexes help?
In this talk, I will help you decipher database query plans and give some rules of thumb to understand if the database is doing the best it can. We will also use query plans to find the best indexes for queries by observing what the database is looking for. I will also share several anti-patterns I have seen in projects and show how to rewrite them in a database-friendly way. Although I will use Python to explain the principles and execute my queries, I will show the raw SQL to make it applicable to any programming language.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/6795/</url><track>App Developer (25 minutes)</track><persons><person id="1342">Aivars Kalvāns</person></persons></event></room><room name="Omega 2"><event id="7134"><start>10:25</start><duration>00:30</duration><room>Omega 2</room><title>Kubernetes from the Database Out</title><abstract>You already know your Postgres, but you're being asked to work with this Kubernetes thing. Do you want to focus your Kubernetes learning on only the bits which are relevant to databases? Then this is the talk for you! Skip the usual 'why run databases on Kubernetes' discussion and dive straight into what you need to know to talk Postgres on Kubernetes.

Using a Postgres database hosted on Kubernetes as an example, I will cover the components of Kubernetes involved in day-to-day activities - including network connectivity, storage, and the automation of restarts and upgrades.

Join me for an overview of the few, core terms and concepts among the many, many pieces of the Kubernetes ecosystem you need to learn about first, to start your Data on Kubernetes journey.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7134/</url><track>DBA (25 minutes)</track><persons><person id="1160">Alastair Turner</person></persons></event></room><room name="Alfa"><event id="6947"><start>10:25</start><duration>00:30</duration><room>Alfa</room><title>Discover your contribution-magic</title><abstract>Let's discover some ways you can make individual contributions to the PostgreSQL project besides the traditional development paths, because everyone who has a point of contact with PostgreSQL is invited to do so. Learn more about how you can contribute with your personal skills and knowledge, even without a technical background. This talk is your introduction to getting involved in the open source world and making it an even better place. Let magic happen to you.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/6947/</url><track>Community (25 minutes)</track><persons><person id="1242">Cornelia Biacsics</person></persons></event></room><room name="Other"><event id="7160"><start>10:55</start><duration>00:30</duration><room>Other</room><title>Coffee Break</title><abstract /><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7160/</url><track>Breaks</track><persons /></event></room><room name="Omega 1"><event id="7059"><start>11:25</start><duration>00:50</duration><room>Omega 1</room><title>PostgreSQL Tips &amp; Tricks For App Devs</title><abstract>PostgreSQL has a huge range of features, maybe too many.  Making use of these features can often make application developer's lives easier, reducing the complexity of their application.

We'll take a look at some use cases I've ran into over the years and what features of PostgreSQL can be used to help solve those problems.

Taking a look at use cases such as:

* Event scheduling &amp; booking
* Task execution
* Searching
* Geolocation
* Unknown data

And more!</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7059/</url><track>App Developer (45 minutes)</track><persons><person id="424">Chris Ellis</person></persons></event></room><room name="Omega 2"><event id="6846"><start>11:25</start><duration>00:50</duration><room>Omega 2</room><title>Flavors of PostgreSQL® and you: how to choose a Postgres</title><abstract>Nearly all the major cloud computing providers provide some sort of “Postgres-compatible” relational database service, but the choice isn’t as simple as picking whichever one your cloud provider offers. Some provide deep integration for AI/ML workloads, and others are serverless databases that aren’t Postgres-related at all. Combined with low awareness of more recent additions to open source Postgres’ feature set, many developers aren’t sure how to proceed in the Postgres in a way that best reflects their needs.

This isn't a vendor talk, however. This talk aims to help developers choose an implementation of Postgres, and understand what they are – and aren't – getting when they choose a proprietary implementation by one of the major cloud vendors or another company. 

Talk outline:
– Intro: What makes Postgres Postgres-y? How has the open source community dealt with forks, rewrites and extensions over time, and how is that relevant to our discussion of ‘modern’ Postgres-derived databases?
– The meat: comparing and contrasting various Postgres-derived databases, understanding their feature sets, what makes them unique and what use cases they’re particularly well suited for
– Google’s AlloyDB Omni, AI/ML capabilities and columnar engines
– Amazon Aurora and Neon, both serverless Postgres-compatible databases, and what we mean by “Postgres compatible’
– TimescaleDB, PostGIS and other specialized extensions of Postgres, and why open source is cool and allows for infinite extensibility
– And of course open source Postgres, and what makes its most recent features relevant in 2025</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/6846/</url><track>App Developer (45 minutes)</track><persons><person id="1348">Celeste Horgan</person></persons></event></room><room name="Alfa"><event id="7037"><start>11:25</start><duration>00:50</duration><room>Alfa</room><title>The SyncRep Detective Story: Chasing Ghosts in PostgreSQL, Finding Demons in Storage</title><abstract>In a high-availability PostgreSQL architecture with sync replicas, a sudden spike in commit latency is a high-stakes crime. In our case, data from pg_wait_sampling pointed to a single, obvious suspect: the SyncRep wait event. This launched a critical investigation to restore our application's performance.

Our initial inquiry took us down a rabbit hole of what we now know was a classic red herring. We were convinced the culprit was network-related, spending valuable time investigating potential network misconfigurations and signs of overload. Yet, despite our best efforts, the evidence never fully added up, and the performance issues persisted.

The breakthrough came when we looked closer at the replica's activity and discovered our "smoking gun": persistently slow fdatasync() calls. This crucial clue exonerated the network and proved the problem wasn't in the transit of data, but in its persistence. The focus of our investigation pivoted instantly and intensely towards the storage layer, where the real mystery lay.

This presentation details our two-pronged counterattack:

The Tactical Containment: As we began the deep-dive into the storage system, we immediately implemented quorum-based synchronous commits. This provided crucial first-aid, reducing the immediate impact on the primary and buying us valuable time.

The Strategic Solution: The core of our story is a deep dive into the custom patch we engineered for PostgreSQL. We will walk through the logic of this patch, designed specifically to reduce the primary's performance sensitivity to slow replica disk writes.

Join this session to learn:

How to use low-level diagnostics to spot slow fdatasync() calls and correctly identify I/O-bound replication lag.

The practical benefits and implementation details of using quorum commits as a powerful mitigation strategy.

A technical breakdown of our PostgreSQL patch and the lessons we learned in modifying the source to solve a unique infrastructure challenge.

This is a real-world story of misdirection, deep-dive forensics, and pragmatic engineering. You will leave with a playbook for diagnosing the true source of replication latency, even when all initial signs point elsewhere.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7037/</url><track>Postgres Internals (45 minutes)</track><persons><person id="1383">Dmitry Fomin</person></persons></event></room><room name="Beta"><event id="7191"><start>11:25</start><duration>00:50</duration><room>Beta</room><title>TDE as an Extension: A Different Path for PostgreSQL Encryption</title><abstract>Transparent Data Encryption (TDE) has been a long-standing challenge in the PostgreSQL community. While proprietary solutions exist and major patch sets have been proposed, the topic continues to spark debate on the hackers mailing list, with no clear path forward.

Our team decided to take a different approach: instead of building TDE directly into PostgreSQL, we explored how far we could go by implementing it as an extension, pushing core changes only where extensibility improvements were needed.

This has been, and still is, a demanding project. Along the way, we have built multiple prototypes, hit dead ends, and uncovered design trade-offs that were not obvious at the start.

In this talk, we will share the technical lessons from our journey: what failed, what succeeded, how our extension-based approach actually works, and which challenges remain unsolved.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7191/</url><track>Sponsors</track><persons><person id="1415">Zsolt Parragi</person></persons></event></room><room name="Other"><event id="7166"><start>12:15</start><duration>01:00</duration><room>Other</room><title>Lunch</title><abstract /><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7166/</url><track>Breaks</track><persons /></event></room><room name="Omega 1"><event id="7054"><start>13:15</start><duration>00:30</duration><room>Omega 1</room><title>Implementing Slowly Changing Dimensions in Postgres</title><abstract>Slowly Changing Dimensions (SCD) are a popular method to model changes of database reference values over time and maintain history data, for example product prices that change over time. When correctly used, they are powerful and provide a structured way to simplify complex data models.
 This talk will review six types of SCDs and discuss how the most relevant type can be modeled in Postgres, and how JSONB, the daterange data type, and the btree_gist extension can be used to create very elegant and powerful SCD implementations in Postgres.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7054/</url><track>App Developer (25 minutes)</track><persons><person id="178">Marc Linster</person></persons></event></room><room name="Omega 2"><event id="7095"><start>13:15</start><duration>00:30</duration><room>Omega 2</room><title>Implementing strong cross-platform resiliency in agile environments with logical replication</title><abstract>Resiliency means that data of critical applications are not lost even in cases of extended and complete downtime of infrastructure providers. In particular, we have to guarantee that no more than 15 minutes worth of data are lost in such a scenario. The issue is exacerbated by the fact that applications may release schema changes at any point in time, without the possibility to allow deployments only during release windows. The obvious solution - physical replication - is not possible because it is not supported by the infrastructure provider. In this talk we show how logical replication in Postgres can be used to implement the required level of resiliency and how we deal with the fact that schema changes are not replicated.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7095/</url><track>DBA (25 minutes)</track><persons><person id="694">Andreas Geppert</person></persons></event></room><room name="Alfa"><event id="7021"><start>13:15</start><duration>00:30</duration><room>Alfa</room><title>They grow up so fast: donating your open source project to a foundation</title><abstract>The first commit to the CloudNativePG project was made in February 2020. Just two years later, EDB began the process of donating the project to the Cloud Native Computing Foundation (CNCF), part of the nonprofit Linux Foundation. This move wasn’t just symbolic—it was a deliberate strategy to ensure CloudNativePG could continue to thrive under the guidance of a broader, more diverse community of contributors.

Transferring stewardship of an open source project to a foundation is a milestone. It’s about more than governance—it’s about trust, neutrality, and long-term sustainability. Becoming part of the CNCF unlocks new levels of visibility, collaboration, and adoption, connecting the project with a global ecosystem of practitioners and end users.

At the time of writing, CloudNativePG is a CNCF Sandbox project. Our hope is to reach Incubation status by the end of next year. But how did we get here—and what does “donating” a project really involve?

Join us for a candid, behind-the-scenes look at the journey of donating an open-source project to a foundation: the motivations, the process, the surprises, and the lessons learned along the way.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7021/</url><track>Community (25 minutes)</track><persons><person id="1171">Floor Drees</person><person id="4">Gabriele Bartolini</person></persons></event></room><room name="Omega 1"><event id="6848"><start>13:55</start><duration>00:50</duration><room>Omega 1</room><title>Long Queries and the Art of Full Scan</title><abstract>Some queries just can’t run in a fraction of a second, no matter how well-written. This does not mean they cannot be optimized.
Many practitioners hold that since analytical reports do not have strict response time requirements, it is not important how fast or slow they run. What's a big deal if a query only runs once a day, or once a week, or once a month? This is a dangerous practice. If report performance is neglected, performance can easily degrade from minutes to hours or even days! 
Let's learn how to be proactive and build reports the right way from the start, so that they won't become a performance disaster when the data volumes increase!</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/6848/</url><track>App Developer (45 minutes)</track><persons><person id="752">Henrietta Dombrovskaya</person></persons></event></room><room name="Omega 2"><event id="6931"><start>13:55</start><duration>00:50</duration><room>Omega 2</room><title>Beyond the How: Why Table Partitioning Truly Matters</title><abstract>Table partitioning has become a well-known technique in the PostgreSQL world. There have been talks about it at most of the conferences I visited last year. But often, we talk about the technicalities of partitioning and not why we partition. This talk is all about the "why" and will set you up for success when you are doing partitioning!

Table partitioning starts with finding the leading figure in your data. Only when you find your leading figure can you partition all tables in conjunction with each other. And when all tables are partitioned around that leading figure, you have to align all the partition boundaries as well! Aligning partitions around your leading figure is crucial for basically all the good that partitioning can offer you. They open the door for:

 - At least not terrible performance
 - Timely partitioning maintenance
 - Out-of-the-box PII compliance
 - Trivial data cleanup
 - Transparent data tiering, moving data to a second storage tier without the application even being aware

I am especially enthusiastic about how easy data tiering becomes after all the tough groundwork we covered over the years.

When partitioning is done wrong, as I did it in the past, performance can and will be terrible. When done in the right way, you can use enable_partitionwise_join and enable_partitionwise_aggregate to make query performance with partitions really work. For me, the difference in performance was a factor of 70 with respect to query run times!

All the applied strategies presented have been battle tested on our biggest, multiple +100TBs, and most pressured databases. As we are processing financial data they are compliant with the strict financial regulations and are fully based on out of the box and open source technologies. 

After this presentation, you will understand all the boundary conditions for building a high-performing, flexible and easy to manage partitioning plan. As a bonus, you get an easier environment to manage, faster vacuums, out-of-the-box PII data compliance, and a very natural way of data cleanup and/or tiering. You and your databases will be ready for whatever data volumes the future will throw at you!</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/6931/</url><track>DBA (45 minutes)</track><persons><person id="859">Derk van Veen</person></persons></event></room><room name="Alfa"><event id="7001"><start>13:55</start><duration>00:50</duration><room>Alfa</room><title>AIO in PG 18 and beyond</title><abstract>PostgreSQL 18 gained support for using asynchronous I/O (AIO) for reads.

This talk will discuss the limitations of AIO in PG 18, the workloads in which it can and can't help, and by how much it can help.

After that we will look ahead to AIO support beyond PG 18.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7001/</url><track>Postgres Internals (45 minutes)</track><persons><person id="140">Andres Freund</person></persons></event></room><room name="Beta"><event id="7185"><start>13:55</start><duration>00:50</duration><room>Beta</room><title>From Chaos to Compliance: How PostgreSQL Makes Regulations Work for You</title><abstract>Compliance often feels like a burden, endless checklists, security audits, and regulations that threaten to slow innovation. But what if compliance could become a strength instead of a roadblock?
In this talk, we’ll explore how PostgreSQL helps organizations meet GDPR, PCI DSS, HIPAA, and other regulatory requirements while keeping systems efficient and scalable. You’ll discover built-in features, practical extensions, and real-world strategies that turn compliance into an enabler of trust, security, and business growth.

1. How PostgreSQL features like RLS, auditing, and encryption make compliance easier than you think
2. Real-world patterns for tackling GDPR, PCI DSS, and HIPAA with PostgreSQL
3. Common compliance pitfalls (and how to avoid them before auditors find them)
4. Turning compliance into a business advantage instead of a bottleneck</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7185/</url><track>Sponsors</track><persons><person id="1409">Raj Verma</person></persons></event></room><room name="Omega 1"><event id="7094"><start>14:55</start><duration>00:50</duration><room>Omega 1</room><title>Table repacking, done right</title><abstract>There's always been a need for a mechanism to get rid of table bloat. VACUUM FULL does that already, but it comes with a potentially long period during which the table cannot be accessed or modified.  Users discover to much frustration that Postgres does not offer any solutions to this problem, and they eventually turn to external tools.

Enter REPACK CONCURRENTLY.  Intended to be integrated in Postgres 19, we hope it will offer peace of mind to thousands of DBAs around the world.  But what is it?  How does it work?  We intend to explain all that every user will need to know about it, and then some.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7094/</url><track>DBA (45 minutes)</track><persons><person id="193">Álvaro Herrera</person><person id="123">Antonin Houska</person></persons></event></room><room name="Omega 2"><event id="7084"><start>14:55</start><duration>00:50</duration><room>Omega 2</room><title>Migrating to PostgreSQL: Strategies, Sovereignty, and Success</title><abstract>Migrating existing database systems can be one of the most complex yet rewarding endeavors for any organization. With PostgreSQL's rising popularity due to its robust feature set, open-source flexibility, and cost-effectiveness, many are looking to transition from proprietary databases like Oracle, MySQL, and Microsoft SQL Server.

This 45-minute talk provides a comprehensive guide to navigating the intricate landscape of database migrations to PostgreSQL. We will delve into various migration strategies, from lift-and-shift to phased approaches, helping you choose the right path for your specific needs. A critical focus will be placed on data sovereignty aspects, discussing how to ensure compliance and maintain control over your data throughout the migration process. We'll explore a range of tooling options, from native PostgreSQL utilities to third-party solutions, and share best practices to minimize downtime and ensure data integrity. Attendees will gain insights into common pitfalls and learn how to avoid them, backed by real-world examples and live demonstrations. Whether you're planning your first migration or looking to optimize an ongoing transition, this session will equip you with the knowledge and confidence to achieve a successful and secure move to PostgreSQL.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7084/</url><track>DBA (45 minutes)</track><persons><person id="907">Raphael Salguero</person></persons></event></room><room name="Alfa"><event id="6887"><start>14:55</start><duration>00:50</duration><room>Alfa</room><title>MultiXacts in PostgreSQL: usage, side effects, and monitoring</title><abstract>PostgreSQL’s ability to handle concurrent access while maintaining data consistency relies heavily on its locking mechanisms, particularly at the row level. When multiple transactions attempt to lock the same row simultaneously, PostgreSQL turns to a specialized structure called MultiXact IDs. While MultiXacts provide an efficient way to manage multiple locks on a single row, they can also introduce performance challenges, such as unexpected slowdowns or delays during vacuum operations.
In this talk, we dive deep into the inner workings of MultiXacts, exploring how they function, where they are commonly used, and the potential side effects they can have on your database performance. You’ll learn how to monitor MultiXacts, identify bottlenecks, and implement strategies to mitigate their impact on your system.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/6887/</url><track>Postgres Internals (45 minutes)</track><persons><person id="804">Divya Sharma</person></persons></event></room><room name="Beta"><event id="7186"><start>14:55</start><duration>00:50</duration><room>Beta</room><title>Pushing Postgres Forward: From Open Source Contributions to Intelligent Tuning</title><abstract>Microsoft’s contributions to PostgreSQL continue to grow, from upstream performance improvements to innovations in Azure Database for PostgreSQL. This talk will focus on our open source work, with a deep dive into automated index tuning—how it works, what it enables, and where it’s going. Expect technical depth, real-world insights, and a look at how Microsoft is helping shape the future of PostgreSQL.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7186/</url><track>Sponsors</track><persons><person id="1410">Adam Wolk</person></persons></event></room><room name="Omega 1"><event id="7093"><start>15:55</start><duration>00:30</duration><room>Omega 1</room><title>Diofanti.org: A Civic Tech Journey Powered by PostgreSQL</title><abstract>What began as a simple script to track my mom’s citizenship case evolved into Diofanti.org—a free civic tech platform monitoring millions of transactions and decisions across the Greek government, all powered by PostgreSQL.

In this talk, I’ll share how PostgreSQL—and its vibrant extension ecosystem—enabled every stage of this unlikely civic tech journey:

- **Phase 1: The Scrappy Script**&lt;br&gt;
Structuring chaotic government PDFs into clean, queryable data using PostgreSQL.

- **Phase 2: Scaling Transparency**&lt;br&gt;
Ingesting massive public datasets via the http extension and custom SQL pipelines.

- **Phase 3: AI for the People**&lt;br&gt;
Powering a chatbot with pgvector-backed semantic search to help citizens ask real questions about their government—and their money.

What started as a personal side project quickly pulled me deeper into PostgreSQL development. Diofanti’s challenges led me to write custom extensions like pgpdf, explore SQL/JSON path internals, and eventually contribute to PostgreSQL core itself.

Whether you’re a developer, open-data advocate, or just someone who loves bending PostgreSQL to your will, this is a story of how a “small script” turned into a platform for civic impact.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7093/</url><track>App Developer (25 minutes)</track><persons><person id="1392">Florents Tselai</person></persons></event></room><room name="Omega 2"><event id="6832"><start>15:55</start><duration>00:30</duration><room>Omega 2</room><title>All about Common Vulnerabilities and exposures in PostgreSQL</title><abstract>Security is always of utmost priority in the computing world and Postgres implements it in several ways. One such way is by having Roles and privileges. The highest privileged role is that of a Superuser. A role that is not a superuser is usually restricted from performing some actions, whether it is installing certain extension or viewing certain tables or altering the database state, unless granted to do so by a superuser itself. However, since Postgres is an open source community product that is constantly adding new features and to run a project using Postgres database involves not only the Postgres binary but hardware and OS on which it is hosted, the application framework , client libraries and various extensions installed, this can sometimes lead to some bugs that enable a non privileged user to perform certain actions or access certain data which it is not granted to. This risks a hacker mounting attacks with serious impact. Therefore it is very important for the DBAs to know how to navigate the CVE landscape, check for CVE announcements and decipher details to analyze impact on his environment and implement minor  fixes whenever applicable. This is also important for users who are hosting their databases on Cloud and check with their cloud providers that the environment is secure and the such vulnerabilities are handled.

My talk will be about:
- What is CVE landscape: CVE, ADP, CVSS, CWE, CNA
- Why it is important?
- What Postgres projects are currently included?
- Postgres Security Releases : timeline, where to check and what to check , enabling notification
- How to report if a user finds a security bug and what actions will follow
- Some example CVEs</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/6832/</url><track>DBA (25 minutes)</track><persons><person id="1088">Priyanka Chatterjee</person></persons></event></room><room name="Alfa"><event id="6932"><start>15:55</start><duration>00:30</duration><room>Alfa</room><title>Don't leak user data to AI - Strategies for protecting PII from LLMs and MCP</title><abstract>MCP has made it incredibly easy for large language models to connect to tools and services, including postgres. With many of the MCP servers that interact with postgres, you can speak to your databases using a combination of everyday language, prompting, and SQL. But over-eager-to-please agents could have your LLM reaching for parts of the Database that you didn't intend for it to look at. This can result in customer information being handed to LLMs which can not only result in unintentional data leaks, but also also violate the law.

This talk reveals some strategies that protects you from LLMs getting hold of PII.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/6932/</url><track>App Developer (25 minutes)</track><persons><person id="1363">Jay MIller</person></persons></event></room><room name="Other"><event id="7161"><start>16:25</start><duration>00:30</duration><room>Other</room><title>Coffee Break</title><abstract /><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7161/</url><track>Breaks</track><persons /></event></room><room name="Omega 1"><event id="7182"><start>17:00</start><duration>00:15</duration><room>Omega 1</room><title>Postgres on AWS: Run 5X faster on metal, migrate anywhere</title><abstract>We'll explore how open-source managed PostgreSQL can deliver both superior performance and portability. By using local NVMe storage instead of network-attached disks, Ubicloud Postgres eliminates the I/O bottlenecks that limit performance in services like AWS RDS.

This keynote covers how Ubicloud Postgres runs on EC2 instances with automated backups, recovery, high availability, and more. It also demonstrates how to achieve up to 5x higher performance.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7182/</url><track>Platinum Sponsor Keynotes</track><persons><person id="1406">Ozgun Erdogan</person></persons></event><event id="7189"><start>17:20</start><duration>00:15</duration><room>Omega 1</room><title>Why PostgreSQL took the crown from MySQL and what lies ahead</title><abstract>In the early 2000s, MySQL was the go-to Open Source database for new projects. Now, two decades later, that's no longer the case. PostgreSQL has become the undisputed leader, winning the trust and mindshare of developers everywhere.So, how did this shift happen? This talk will explore what caused PostgreSQL's rise and MySQL's relative decline. We'll also look at the future of PostgreSQL and the challenges it needs to navigate to maintain its position as the top open-source database.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7189/</url><track>Platinum Sponsor Keynotes</track><persons><person id="1413">Peter Zaitsev</person></persons></event><event id="7183"><start>17:40</start><duration>00:15</duration><room>Omega 1</room><title>PostgreSQL in ever more critical environments</title><abstract>PostgreSQL has grown and is now powering highly critical platforms. But what are the challenges and what is needed to achieve success? Let us dive in and find out ...</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7183/</url><track>Platinum Sponsor Keynotes</track><persons><person id="1407">Hans-Jürgen Schönig</person></persons></event></room></day><day date="2025-10-24"><room name="Other"><event id="7172"><start>08:30</start><duration>00:30</duration><room>Other</room><title>Registration</title><abstract /><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7172/</url><track>PGConf.EU</track><persons /></event></room><room name="Omega 1"><event id="7175"><start>09:00</start><duration>00:15</duration><room>Omega 1</room><title>Day 3 Welcome</title><abstract /><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7175/</url><track>PGConf.EU</track><persons><person id="667">Karen Jex</person></persons></event><event id="7102"><start>09:25</start><duration>00:50</duration><room>Omega 1</room><title>Transform your development workflow with thin cloning</title><abstract>Have you ever run into:
- Schema differences between development and production?
- Slow queries in production, but they were fast in development?
- Bugs that happen in production but do not replicate in development, because only the exact way the data exists in production causes the bug?

At Academia.edu, we have experienced all of the above. Wouldn't it be great if we could just debug everything in production? With database "thin cloning" you (kind of) can!

In this talk, we will cover what "thin cloning" is, how you can use tools like DBLab Engine or Aurora cloning, and how it has transformed development workflows at Academia.edu.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7102/</url><track>App Developer (45 minutes)</track><persons><person id="1393">Nicholas Meyer</person></persons></event></room><room name="Omega 2"><event id="7016"><start>09:25</start><duration>00:50</duration><room>Omega 2</room><title>PostgreSQL as a Graph Database: Who Grabbed a Beer Together?</title><abstract>Graph structures can reveal patterns in connected data that traditional relational models miss, such as how communities form and evolve over time. In this session, we will explore why graph modeling is important for these types of analyses and how PostgreSQL can serve as a powerful graph database. We will compare available extensions including Apache AGE, pgRouting, and pgGraph, and discuss their strengths and recommended use cases.

Then, through a live demo using data about speakers from previous PGConf events combined with Untappd check-ins, we will visualize social interactions and shared experiences, showing how to uncover insights like who connected with whom, popular gathering spots, and how the conference community network changes over time, all with PostgreSQL.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7016/</url><track>Community (45 minutes)</track><persons><person id="604">Taras Kloba</person></persons></event></room><room name="Alfa"><event id="6933"><start>09:25</start><duration>00:50</duration><room>Alfa</room><title>Hazards of logical decoding in PostgreSQL</title><abstract>Logical decoding was introduced in PostgreSQL 9.4 and is being constantly improved. It has enabled many new applications. The extensible mechanism of output plugins and in-core logical replication based on logical decoding make this feature truly exciting.

One popular use case of this feature is implementing the Change Data Capture (CDC) pattern. Although developers are usually eager to adopt this modern approach to leverage its apparent benefits, I strongly believe that using logical decoding in PostgreSQL requires at least a basic understanding of its implementation and should be treated with great care.

In this talk, I will share the problems we, as Zalando's DBaaS team, encountered while adopting and maintaining our internal CDC solution based on logical decoding. I will also highlight the nuances you should always keep in mind when using this technology.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/6933/</url><track>Postgres Internals (45 minutes)</track><persons><person id="873">Polina Bungina</person></persons></event></room><room name="Beta"><event id="7192"><start>09:25</start><duration>00:50</duration><room>Beta</room><title>Lessons from two decades of hacking the proprietary value into open source databases</title><abstract>Two decades of working with different open source databases have taught us a lot about what it takes to make them enterprise-ready while keeping them truly open. Features like high availability, Transparent Data Encryption (TDE) and OpenID Connect (OIDC) aren’t just “nice to have” — they’re what determine whether a database can succeed in the Enterprise environment.

In this talk, we’ll explore how those lessons apply to PostgreSQL. We’ll discuss where Postgres follows familiar patterns from other open source databases, where it stands apart, and what that means for adoption in large organizations. We’ll also dive into the current state of making PostgreSQL fit for enterprise workloads, highlight ongoing gaps, and share ideas for what the community could focus on to ensure PostgreSQL’s continued growth and success.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7192/</url><track>Sponsors</track><persons><person id="1416">Michal Nosek</person></persons></event></room><room name="Omega 1"><event id="7045"><start>10:25</start><duration>00:30</duration><room>Omega 1</room><title>An Introduction to B-trees and LSM-trees for DEVs and DevOps</title><abstract>This introductory talk for DEVs and DevOps will focus on 
* Why you’re likely to be working with both B-trees and LSM-trees in the future
* Key differences between B-trees and LSM-trees, and surprising gotchas when switching workloads between them</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7045/</url><track>App Developer (25 minutes)</track><persons><person id="797">Dave Pitts</person></persons></event></room><room name="Omega 2"><event id="6891"><start>10:25</start><duration>00:30</duration><room>Omega 2</room><title>Fast-path locking improvements in PG18</title><abstract>Let's talk about the improvement in fast-path locking in upcoming PG18, which can bring substantial speedups on systems with many cores and/or queries accessing many relations (where "many" may mean "more than 16", and it includes indexes). This is particularly visible with partitioning, but easy to hit even without it.

I'll start by explaining how fast-path locking works, why it was introduced, and why it doesn't help with more relations. Then I'll explain how it was extended in PG18, and present some benchmark numbers to quantify the improvements.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/6891/</url><track>Postgres Internals (25 minutes)</track><persons><person id="116">Tomas Vondra</person></persons></event></room><room name="Alfa"><event id="6990"><start>10:25</start><duration>00:30</duration><room>Alfa</room><title>Waiting for Commit</title><abstract>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. To see this we will go on a journey that a commit takes through a replicated cluster and all the hazards it meets on the way. How head-of-line blocking can escalate minor storage tail-latency issues on replica to a major performance problem for the whole system. What tools you can use to track down the source of the problem and what solutions are available to mitigate it.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/6990/</url><track>DBA (25 minutes)</track><persons><person id="868">Ants Aasma</person></persons></event></room><room name="Other"><event id="7162"><start>10:55</start><duration>00:30</duration><room>Other</room><title>Coffee Break</title><abstract /><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7162/</url><track>Breaks</track><persons /></event></room><room name="Omega 1"><event id="7018"><start>11:25</start><duration>00:50</duration><room>Omega 1</room><title>Patroni: what the blog posts don't tell you...</title><abstract>Patroni has become the Gold Standard for managing High Availability Postgres clusters. It has great documentation and there are hundreds of blog posts detailing how to set up your first cluster.

However, there is a large gap between the blog posts and having a production ready system that you actually trust.

This talk will briefly describe a typical Patroni setup before discussing/demonstrating the following topics that the blog posts never have enough space for!

- Security hardening for Patroni, HAProxy, etcd and Postgres
- Proxy layer considerations
- Configuration best practice: what goes in the DCS?
- Tips and tricks for managing several Patroni clusters
- Backups
- Upgrades
- Failover testing

Whether you are looking to build your first Patroni cluster or you already run several, there should be something in this talk for you!</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7018/</url><track>DBA (45 minutes)</track><persons><person id="966">Cameron Murdoch</person></persons></event></room><room name="Omega 2"><event id="7128"><start>11:25</start><duration>00:50</duration><room>Omega 2</room><title>The Good, The Bad, and The Bloated: An Autovacuum Story</title><abstract>Picture this: 3 autovacuum workers facing down 1,500 tables in a deadly standoff. The result? A bloated, slow database that forced a midnight dump/restore showdown.

This talk will tell you everything you need to know about autovacuum: from the fundamentals of how it works to real-world production disasters to smart tuning strategies. 

You'll see what happens when autovacuum configurations go wrong, learn proper tuning approaches that keep databases running smoothly, and discover how PostgreSQL's observability helps you become the sheriff your databases need.

Starting with autovacuum internals, we'll walk through actual production scenarios (including that 3-vs-1500 shootout), demonstrate how to spot trouble before it starts, and provide concrete strategies for turning autovacuum from potential foe into reliable friend.

You'll leave knowing how to configure autovacuum properly for your workload, use PostgreSQL's observability tools effectively, and ride off into the sunset with a perfectly tuned database.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7128/</url><track>DBA (45 minutes)</track><persons><person id="1136">Jérémie Grauer</person></persons></event></room><room name="Alfa"><event id="7140"><start>11:25</start><duration>00:50</duration><room>Alfa</room><title>Panel Discussion: How to Work with Other Postgres People</title><abstract>Lack of awareness around Mental Health issues has always been a problem in IT circles, leading to stress, burnout and difficulties in workplace and community relationships. This often results in employee turnover and strained dynamics within open source projects, and creates barriers for achieving a diverse contributor base.

Building on the recognition that we are all different, this panel will address the challenges faced by contributors within the PostgreSQL ecosystem. Drawing on insights into neurodivergence and mental health contributed by community members, we'll explore tangible strategies for fostering a culture that promotes psychological well-being and respect for diverse needs and communication styles. 

Emphasizing practical tools like personal "README" guides, supportive communication practices, and conflict resolution techniques, the discussion aims to identify actionable ways to mitigate common stress points and support contributors effectively.

We hope to make PostgreSQL a leading example of inclusivity and collaboration in open source, attracting and retaining a community of contributors who feel respected, supported, and empowered.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7140/</url><track>Community (45 minutes)</track><persons><person id="541">Boriss Mejias</person><person id="1171">Floor Drees</person><person id="323">Jimmy Angelakos</person><person id="667">Karen Jex</person></persons></event></room><room name="Beta"><event id="7190"><start>11:25</start><duration>00:50</duration><room>Beta</room><title>Monitoring Managed Postgres, the OSS Way</title><abstract>Observing and analyzing PostgreSQL behavior to identify performance bottlenecks is a key feature for a managed Postgres offering.
In this talk, we will walk through a simple yet powerful setup to monitor PostgreSQL server performance in a managed cloud offering, based on open-source tools like postgres_exporter, VictoriaMetrics and Grafana. Using this setup, we will explore a methodology to decide which OS and Postgres metrics matter most, along with key signals to use for alerting. Lastly, we will go through some examples on how to investigate performance issues, with a focus on some new areas of adoption like vector storage.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7190/</url><track>Sponsors</track><persons><person id="1414">Shikhar Bhardwaj</person></persons></event></room><room name="Other"><event id="7165"><start>12:15</start><duration>01:00</duration><room>Other</room><title>Lunch</title><abstract /><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7165/</url><track>Breaks</track><persons /></event></room><room name="Omega 1"><event id="7120"><start>13:15</start><duration>00:30</duration><room>Omega 1</room><title>Building Tetris in a SQL Query!</title><abstract>Recursive CTE queries have been gaining special attention in recent years, as they enable complex computations to occur closer to the data source, rather than loading large amounts of data to an external application.

This presentation aims to shed light on recursive CTEs in PostgreSQL, including use cases, key considerations when using them, and current limitations. To exemplify just how powerful CTEs are, a fully working game of Tetris is implemented in a PostgreSQL query.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7120/</url><track>App Developer (25 minutes)</track><persons><person id="1387">Nuno Faria</person></persons></event></room><room name="Omega 2"><event id="7112"><start>13:15</start><duration>00:30</duration><room>Omega 2</room><title>Tracking plan shapes over time with Plan IDs and the new pg_stat_plans</title><abstract>In this session I'll share an overview of my recent work to improve plan ID tracking in Postgres (similar to query ID tracking), and how it enables aggregate analysis of which query used which plan structure. We'll discuss which parts of a plan should be considered significant, and how to deal with special cases such as partitioning (which can lead to many unique plan IDs), and which parts of this could be done better in-core, vs an extension.

We will explore our new pg_stat_plans extension (similar in spirit to the same named but no longer maintained original pg_stat_plans) that builds on improvements in Postgres 18 to allow low-overhead monitoring of query plans over time.

We'll also compare how the new pg_stat_plans relates to previous approaches, including the old pg_stat_plans and pg_store_plans open-source extensions, as well as proprietary implementations by cloud providers that I'm familiar with as a user.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7112/</url><track>DBA (25 minutes)</track><persons><person id="220">Lukas Fittl</person></persons></event></room><room name="Alfa"><event id="6877"><start>13:15</start><duration>00:30</duration><room>Alfa</room><title>How to explain PostgreSQL to kids</title><abstract>What if your kid asked you "What’s this Postgres thingy you work on?".  Well, you could say that PostgreSQL is like a giant toy box with lots of different compartments: blocks in one spot, balls in another, and puzzles in their own place. But kids don't stop at one question, and they are unapologetically honest: "That's it? What's so cool about it?" Then you have to think about how to explain extensibility and advanced SQL compliance to them ...

You could try the following: This giant toy box can add new kinds of toys and modify existing ones — you can make your own special toys and put them in the box. That’s extensibility! It knows lots of ways to find toys — even tricky ones that are hiding under other toys, and it can follow smart instructions like “find all the red balls that are bigger than this size and were put in the box last week”. That's advanced SQL compliance!

Hopefully your kid will be quite interested in what you work on at this point, but you know what's next - another question "Cool — can I play with friends? Will the giant toy box fix my broken toys?" ... Join this talk for some fun, relatable analogies and storytelling techniques to break down the Postgres database’s sophisticated ideas into understandable, engaging narratives with children! Whether you’re a parent, teacher, or developer, discover how to share your passion for the PostgreSQL database and inspire the next generation with creativity.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/6877/</url><track>Community (25 minutes)</track><persons><person id="1173">Naisila Puka</person></persons></event></room><room name="Omega 1"><event id="6866"><start>13:55</start><duration>00:50</duration><room>Omega 1</room><title>The Lifecycle of a SELECT: A Glimpse into the Depths of PostgreSQL Internals</title><abstract>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.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/6866/</url><track>App Developer (45 minutes)</track><persons><person id="1294">Sergey Dudoladov</person></persons></event></room><room name="Omega 2"><event id="7105"><start>13:55</start><duration>00:50</duration><room>Omega 2</room><title>Breaking PostgreSQL - Learning by doing it wrong</title><abstract>Although PostgreSQL is a very reliable and robust database management system, there are things you shouldn't do. In this session we're breaking PostgreSQL in several ways, live, without any slides (slides will be provided anyway, don't worry). There is no better way to learn as learning from mistakes, isn't it? We're going to take that serious and I am sure you'll have a lot of fun and gain some interesting insights. By the end of this talk you should have a solid understanding of what not not do (and why not)and this will safe you quite some time in your journey with PostgreSQL.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7105/</url><track>DBA (45 minutes)</track><persons><person id="386">Daniel Westermann</person></persons></event></room><room name="Alfa"><event id="7010"><start>13:55</start><duration>00:50</duration><room>Alfa</room><title>We have multiple concurrent versions of this title trying to understand MVCC</title><abstract>When you create, update or delete a row in PostgreSQL, you are actually creating a new version of the row, hence, each row in PostgreSQL may have multiple versions during its life, sometimes many versions concurrently. These multiple versions are the key to different transaction isolation levels, consistent snapshots, and everything around concurrency control. Understanding how multi-version concurrency control (MVCC) works will open you many doors and windows about PostgreSQL internals, vacuum, and visibility of rows within a transaction.

In this talk we will show with concrete examples the MVCC principle, how to observe it and how to monitor the impact it has with the entire system, as it is interconnected with locks, vacuum, and consistency. You will learn when to use transactions with “repeatable reads” or with “read committed” mode, to design better applications. We will see how MVCC is at the core of understanding Postgres.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7010/</url><track>Postgres Internals (45 minutes)</track><persons><person id="541">Boriss Mejias</person></persons></event></room><room name="Beta"><event id="7188"><start>13:55</start><duration>00:50</duration><room>Beta</room><title>Delivering High Availability, Reliability, Scalability, and Low Latency for PostgreSQL Deployments of Any Size</title><abstract>pgEdge believes in the power of PostgreSQL and everything that has contributed to it. That's why we've provided pgEdge Distributed PostgreSQL entirely under the standard PostgreSQL license and releasing pgEdge Enterprise Postgres, to bring you 100% open source, standard PostgreSQL fully optimized for high availability (for both distributed and non-distributed workloads), and more. Scale from a single instance of Postgres, easily implement high availability with read replicas and Patroni, and ultimately grow to globally distributed PostgreSQL architecture across multiple geographies for extreme high availability and low latency requirements. Move with freedom knowing your infrastructure will grow easily with your organization. We'll be here to support you along the way.
Attend this session to learn how to leverage pgEdge Enterprise PostgreSQL to support your operations and scale from any point, whether you're running a single-instance or already hosting a fleet of deployments.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7188/</url><track>Sponsors</track><persons><person id="1412">Ahsan Hadi</person></persons></event></room><room name="Omega 1"><event id="7082"><start>14:55</start><duration>00:50</duration><room>Omega 1</room><title>Can PostgreSQL Compete with Analytics Specialists?</title><abstract>Can PostgreSQL really compete with DuckDB and ClickHouse for analytics workloads? The answer might surprise you!

This session examines PostgreSQL's capabilities in the analytics space and how it stacks up against specialized engines. We'll explore what's possible when you properly tune PostgreSQL for analytical workloads and discover where it excels versus where purpose-built tools shine.

Beyond raw performance comparisons, we'll tackle the critical decision every team faces: when should you stick with PostgreSQL and when is it time to adopt specialized tools? Through practical decision criteria and real-world considerations, we'll establish clear guidelines that go beyond benchmarks. PostgreSQL's versatility, operational simplicity, and massive ecosystem often make it the pragmatic choice for far more analytics scenarios than commonly believed.

Stop assuming you need specialized tools for every analytical workload. Learn when PostgreSQL is "good enough" and when it's time to reach for purpose-built analytics engines. Sometimes the most pragmatic choice is sticking with the reliable workhorse you already know and trust.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7082/</url><track>App Developer (45 minutes)</track><persons><person id="387">Lætitia AVROT</person></persons></event></room><room name="Omega 2"><event id="7116"><start>14:55</start><duration>00:50</duration><room>Omega 2</room><title>CTRL+Z for your Database : Mastering Backup and Recovery in PostgreSQL</title><abstract>What if you could hit CTRL+Z when your production database crashes, someone drops a critical table, or a cloud region outage takes your system offline?   

In this talk, we’ll explore how to build a disaster-resilient PostgreSQL system, one that not only backs up data efficiently but also recovers gracefully when the unexpected happens.     

From traditional SQL dumps to the new incremental backup feature introduced in PostgreSQL 17, we’ll cover practical strategies you can use in real-world environments.

Key Takeaways :     
1) Why backups matter and how to choose the right type for your use case   
2) PostgreSQL backup options: logical vs physical, full vs incremental   
3) Point-in-Time Recovery (PITR), WAL archiving, delayed replicas, and failover testing   
4) What's new in PostgreSQL 17: pg_basebackup with incremental mode, pg_combinebackup, and --filter in pg_dump   
5) How to design PostgreSQL systems for durability, high availability, and quick recovery     

Whether you're managing a single instance or a fleet of databases in production, this session will help you build a resilient PostgreSQL environment ready to handle real-world challenges with confidence and control.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7116/</url><track>DBA (45 minutes)</track><persons><person id="1394">Sakshi Nasha</person></persons></event></room><room name="Alfa"><event id="6825"><start>14:55</start><duration>00:50</duration><room>Alfa</room><title>Database in Distress: Testing and Repairing Different Types of Database Corruption</title><abstract>In recent years, I had to repair several corrupted PostgreSQL databases and have seen many different problems. In some cases corrupted data can even crash the session reading it. To better understand these issues and test different strategies for repairs, I created a Python application that surgically creates various types of damages. This talk demonstrates, through practical examples and outputs from the pageinspect extension, different types of data corruption. Why we see specific errors and how to diagnose these issues. PostgreSQL 18 sets checksums ON by default in initdb, therefore talk also shows how checksums can help to detect damaged pages and "zero them out". It also proposes some improvements that could help to handle corrupted data more effectively on already existing databases which do not use checksums.

Takeaways:
- PostgreSQL databases can suffer from various types of corruption 
- Understanding heap table structure is essential for analyzing different types of errors
- Data page checksums are the best tool for skipping damaged pages
- Without checksums only pages with clearly corrupted header can be removed using the zero_damaged_pages = on setting
- Other types of corruption might require time-consuming salvaging operations
- Improvements in PostgreSQL code and/or new settings could make some repairs less painful on databases without checksums</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/6825/</url><track>Postgres Internals (45 minutes)</track><persons><person id="316">Josef Machytka</person></persons></event></room><room name="Other"><event id="7163"><start>15:45</start><duration>00:30</duration><room>Other</room><title>Coffee Break</title><abstract /><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7163/</url><track>Breaks</track><persons /></event></room><room name="Omega 1"><event id="7167"><start>16:15</start><duration>00:45</duration><room>Omega 1</room><title>Lightning Talks</title><abstract>A series of short talks, each a maximum of 5 minutes long, that were submitted by attendees and selected during the conference itself:

1. Philippe Nöel - From Idea to CREATE EXTENSION: 4 Lessons from Building a Text Search Extension
2. Hans-Jürgen Schönig - pg_crash Making crashes great again
3. Martín Marques and Laura Minen - Do you want to enjoy the great things of life, and… Postgres?
4. Ellert van Koperen - Something about Selectivity
5. Jobin Augustine - Distilling 20 Years of Notes
6. Luigi Nardi - Guessing application owner desires - How to select important query groups without asking the app owner
7. Celeste Horgan - Why the *($&amp;*(#&amp;$ would you volunteer to be on a Code of Conduct Committee
8. Sebastian Jung - Digitizing a public heating network with PostgreSQL in Germany
9. Haritabh Gupta - postgres_fdw evolution, use-cases, limitations
10. Pavlo Golub - CONFELO - Stress-free Conference Talk Selection

For details on how the talks were submitted/selected, see: https://2025.pgconf.eu/attendee-info/lightning-talks/.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7167/</url><track>PGConf.EU</track><persons /></event><event id="7169"><start>17:00</start><duration>00:15</duration><room>Omega 1</room><title>So long, and thanks for all the fish</title><abstract>Closing remarks of the conference. Join us for the now traditional light hearted review and wrap up the events of the week.</abstract><url>https://www.postgresql.eu/events/pgconfeu2025/schedule/session/7169/</url><track>PGConf.EU</track><persons><person id="2">Dave Page</person><person id="1">Magnus Hagander</person></persons></event></room></day></schedule>