Firefly2026-09-102026-09-101https://www.postgresql.eu/events/pgdaynl2026/schedule/08:1800:42Otherhttps://www.postgresql.eu/events/pgdaynl2026/schedule/session/8433/Breaks09:1500:45Cloud NineAt this time of the year, PostgreSQL is rapidly approaching the new release, and we have a pretty clear picture of what will be in PostgreSQL 19. This presentation will give a rapid walk-through of what's most likely to be part of the new version, as well as some things that might still be on the fence for inclusion.https://www.postgresql.eu/events/pgdaynl2026/schedule/session/7772/45 minutesMagnus Hagander09:1500:25The PitThe database management system market has long been dominated by proprietary solutions, increasingly associated with rising costs, vendor lock-in, and strategic dependency. With PostgreSQL, a mature open-source alternative exists that is not only functionally competitive but often technically superior. In the context of digital sovereignty, PostgreSQL is becoming a strategic necessity rather than just a technical choice. This talk presents a practical, experience-driven approach to migrating from proprietary systems to PostgreSQL, covering the entire lifecycle from architectural planning to operations and long-term support. We explore real-world scenarios ranging from simple lift-and-shift to complex transformations, while discussing typical risks, decision frameworks, and common pitfalls. Finally, we examine how organizations can achieve true digital independence and cost reduction through open-source adoption, delivering a clear blueprint for success.https://www.postgresql.eu/events/pgdaynl2026/schedule/session/8411/SponsorsPatrick Lauer10:1000:25Cloud NineWhere and how to host your PostgreSQL comes with a range of tradeoffs, usually cost and performance related. With cloud vendors with turn-key style services seemingly becoming default choices, but at what cost. This talk will take a look at the different tradeoffs of where and how to host your PostgreSQL database. We'll cover ways in which you can benchmark your infrastructure and how different solutions can affect performance vs cost. Looking at things like: - Ways to benchmark and understand storage and PostgreSQL performance - Local vs network attached storage and how this affects performance - Can we make network attached storage almost as fast as local storage - How availability comes into play - How replication and data safety requirements can affect things - How does performance for price compare - Tradeoffs of self hosting And trying to answer the fun question, is PostgreSQL on my Raspberry Pi faster than some common cloud offerings? If so, at what cost?https://www.postgresql.eu/events/pgdaynl2026/schedule/session/7843/25 minutesChris Ellis10:1000:25The PitYou know your PostgreSQL environment inside out. But do you know what it's actually costing — and why? PostgreSQL on Azure is priced for technical performance, not for your wallet. Storage that grows but never shrinks. IOPS tied to storage tiers instead of your workload. High availability on by default, doubling the bill. Backups kept for 35 days because nobody changed the setting. These aren't bugs, they're decisions no one made on purpose. In this session we introduce OptimaSure, OptimaData's Azure FinOps consultancy, combining CloudXcellence tooling with hands-on experience. We walk through the costliest misconfigurations we see in real-world Azure PostgreSQL environments and then go further, with a live demo of CloudXcellence showing hidden cost drivers across PostgreSQL, VMs and your wider Azure setup in real time. The kind of insight that turns a DBA into the person who just saved the company serious money.https://www.postgresql.eu/events/pgdaynl2026/schedule/session/8410/SponsorsGerard ZuidwegHenk van der Valk10:3500:25Otherhttps://www.postgresql.eu/events/pgdaynl2026/schedule/session/8434/Breaks11:0000:30Cloud NineThe new CTO of the company has decided that now we will use PostgreSQL for everything. Not "almost" everything, but really everything. Not only will new projects be deployed using PostgreSQL, but everything running other databases must progressively migrate to PostgreSQL, including NoSQL databases, warehouses, lakehouses, and analytics... everything! The question is: as much as we love PostgreSQL, should we implement such a policy for everything?https://www.postgresql.eu/events/pgdaynl2026/schedule/session/8432/DebateFloor DreesMarc LinsterMayuresh Suresh BagayatkarOlena KutsenkoSebastiaan Alexander Mannem11:3500:45Cloud NineOptimizer hints are instructions to a (relational) database on how a specific SQL query should be executed. Unlike other relational databases such as Oracle, SQL Server or MySQL, PostgreSQL has traditionally not provided the DBA with optimizer hints. The developers’ position was that optimizer issues are bugs to be fixed, which is not always possible in practice, however. Besides optimizer hints, PostgreSQL has always had the ability to influence the planner’s decisions by modifying optimizer parameters. Furthermore, the external pg_hint_plans extension enables optimizer hints and has been available for some time. In the upcoming version 19 of PostgreSQL, optimizer hints will be available directly within PostgreSQL for the first time. This presentation provides an overview of the various ways to influence the PostgreSQL optimizer. It also uses examples to demonstrate how the pg_hint_plans extension and the optimizer hints in PostgreSQL 19 can be used.https://www.postgresql.eu/events/pgdaynl2026/schedule/session/7815/45 minutesMichael Banck11:3500:45The PitEvery team wants to connect an AI agent to their database. Nobody trusts it in production. The problem isn't text-to-SQL (that part is mostly solved). The problem is everything else: the agent doesn't know which tables are deprecated, which columns contain PII, or why three tables named users_* exist. And when something goes wrong, you have no idea which agent ran what query, or why. In this talk, I'll show you how to build a governed AI data layer for Postgres using pg-airman-mcp, an open-source MCP server. Instead of dumping schemas and hoping for the best, we'll use three capabilities that change the game: First, a semantic knowledge base that lets agents search your schema by meaning, not by name. The agent asks "where do we store customer emails?" and gets the right table, along with its PII annotations and deprecation status, without scanning every table in the catalog. Second, semantic aliases: named, reusable queries that your team curates and the agent discovers through natural language. Think of them as a library of blessed queries your agent can find and execute, with built-in role-switching for access control. Third, purpose-tagged connections that stamp every database session with the agent's intent (credit-scoring, fraud-detection, analytics-pipeline) so your DBA can see exactly who is asking what, directly in database logs. You'll walk out with a clear architecture for giving AI agents database access you'd actually approve for production.https://www.postgresql.eu/events/pgdaynl2026/schedule/session/7798/45 minutesBilge Ince12:2001:00Otherhttps://www.postgresql.eu/events/pgdaynl2026/schedule/session/8435/Breaks13:2000:05Cloud NineMany conferences offer 5-minute lightning talks. It’s often seen and promoted as a great way for new speakers to get into public speaking. Or not? It’s a great idea, as long as you’re aware of the risks, especially for introverts. In this lightning talk, I’ll share my first speaking experience and learnings - exactly one year later.https://www.postgresql.eu/events/pgdaynl2026/schedule/session/7779/Lightning TalkCornelia Biacsics13:2500:05Cloud NineWhen data keeps growing, partitioning is always the answer, right? Sometimes partitioning has a knock-on effect that can have serious repercussions. I will show a real-life example of such a case, and the simple way that it was resolved.https://www.postgresql.eu/events/pgdaynl2026/schedule/session/7881/Lightning TalkEllert van Koperen13:3000:05Cloud NineTransparent Data Encryption (TDE) has long been a highly requested feature in the PostgreSQL ecosystem. The pg_tde project aims to fill this gap by providing encryption at rest with minimal impact on existing workflows and applications. In this lightning talk, I’ll present the current status of pg_tde, including recent progress, architecture highlights and key decisions. We’ll go over what’s already working, what challenges remain and how to get involved. Whether you’re interested in security, compliance or PostgreSQL internals, this update will give you a quick but meaningful look at where PostgreSQL is with TDE and how it’s evolving.https://www.postgresql.eu/events/pgdaynl2026/schedule/session/7795/Lightning TalkJan Wieremjewicz13:3500:05Cloud NineClickHouse is building a growing ecosystem of PostgreSQL integrations aimed at analytical workloads and high-volume observability. In this lightning talk, I’ll give a quick technical overview of two open-source extensions: pg_clickhouse, which uses FDW pushdown to execute analytical PostgreSQL queries in ClickHouse and pg_stat_ch, which exports raw per-query execution events from PostgreSQL into ClickHouse for external aggregation and analysis. The goal is to provide a concise introduction to the emerging “Postgres + ClickHouse” stack and the technical direction behind it.https://www.postgresql.eu/events/pgdaynl2026/schedule/session/8378/Lightning TalkGülçin Yıldırım Jelinek13:5000:45Cloud NineBuilding a vector search prototype is easy; keeping it running in production is a completely different problem. When developers push millions of high-dimensional embeddings into PostgreSQL, the physical limits of the database hit hard. Massive vector columns trigger heavy TOAST usage, evict critical data from shared_buffers, and cause storage footprints to explode, usually leaving DBAs to fix the resulting performance degradation. Using data from real-world experiences, we will expose what actually happens to your infrastructure and query plans when vector tables grow exponentially and analyze the trade-offs between space utilization, query latency and recall. Finally, we will explore how to shrink the storage and RAM footprint using halfvec (float16) and binary quantization, while measuring the cost to search accuracy.https://www.postgresql.eu/events/pgdaynl2026/schedule/session/7786/45 minutesMiguel Toscano13:5000:25The PitPostgreSQL 19 is just around the corner. Let's have a look at what's new in that release, what got removed, and why CYBERTEC is happy to be part of the development process. This is my take on why 19 is going to be a great release.https://www.postgresql.eu/events/pgdaynl2026/schedule/session/8412/SponsorsChristoph Berg14:4500:25Cloud NineWhenever any simple switchover needed to be done, it took hours. The customer was killing the primary postmaster out of desperation because it was simply too long. It was reproducing perfectly every time, in every single production and most non-production environments. Was postgres hanging? Was it slow to finish something? Could some application hang a primary shutdown like this? We will discuss debugging on Kubernetes, following the thread and debugging logical replication protocols, along with some simple pg_walreceiver patcheshttps://www.postgresql.eu/events/pgdaynl2026/schedule/session/7793/25 minutesYoann La Cancellera14:4500:25The PitWhat if you could go from a PostgreSQL data model to a fully functional, professional-looking application in a single step? During this session, I’ll show you how Pulsar radically speeds up development, without compromising on quality, flexibility or collaboration. Pulsar is not Low-Code. Not Heavy-Code. It is Smart-Code. That means: * ⁠The speed of Low-Code; * ⁠The freedom and control of traditional development; * ⁠And the intelligence of reusable, model-driven logic. Pulsar bridges the gap between disciplines: * ⁠DBAs: the data model remains the guiding principle * ⁠Developers: maximum productivity without limitations * ⁠Users: intuitive and powerful applications This is not a theoretical concept, but a practical demonstration of how you can build more, with less complexity and make a bigger impact. Get inspired and discover how Pulsar redefines application development, built on PostgreSQL.https://www.postgresql.eu/events/pgdaynl2026/schedule/session/8409/SponsorsRob Sijmons15:1000:25Otherhttps://www.postgresql.eu/events/pgdaynl2026/schedule/session/8436/Breaks15:3500:25Cloud NineWhile the Third Normal Form (3NF) is the gold standard for transactional integrity, it often struggles with complex analytical tasks. Traditionally, bridging the gap between a transactional OLTP model and an analytical Star Schema required the use of third party ETL tools. But as Postgres has matured, the "database-as-a-platform" approach allows us to handle this transformation natively. This talk explores three distinct architectural paths to transforming data from transactional to analytical models within Postgres: 1) Views 2) Materialized Views 3) Triggers All three approaches benefit from a combination with logical replication to build a dedicated analytical replica without impacting transactional performance. The talk dives into the implementation details of each, comparing them across three axes: data freshness, write-amplification cost, and architectural complexity. Attendees will leave with a clear framework for deciding which Postgres technique to use when.https://www.postgresql.eu/events/pgdaynl2026/schedule/session/7820/25 minutesMarc Linster15:3500:25The PitLet'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.https://www.postgresql.eu/events/pgdaynl2026/schedule/session/7788/25 minutesCornelia Biacsics16:0500:25Cloud NineThe Cyber ​​Resilience Act is an EU regulation that came into force in 2024 and will take full effect in the coming years. It obligates software manufacturers to implement specific measures to ensure the security and quality of the software they produce. These measures include, for example, clearly defined procedures for providing security updates. Special rules apply to open-source software and to companies that sponsor open-source projects. PostgreSQL in enterprise use will almost certainly fall under these rules. Due to the unique structure of the PostgreSQL community, with its loose organization, numerous participating companies, and stakeholders worldwide, determining which rules apply to whom is a challenge. In this presentation, I would like to begin to explore what this law means for the PostgreSQL project and its community, which measures the various parties should take, and how this can improve the security and quality of the software.https://www.postgresql.eu/events/pgdaynl2026/schedule/session/7778/25 minutesPeter Eisentraut