-
Maurizio De Giorgi (CERN), Markus Wanner06/02/2026, 10:00Day 1
Welcome from the organizing team, logistics info and notices, sponsors presentation and special thanks
Go to contribution page -
Dr Jaroslav Guenther (CERN), Konstantina Skovola06/02/2026, 10:05Day 1
The CERN Tape Archive (CTA) stores over one exabyte of scientific data. To orchestrate storage operations (archival) and access operations (retrieval), the CTA Scheduler coordinates concurrent data movements across hundreds of tape servers, relying on a Scheduler Database (Scheduler DB) to manage the metadata of the in-flight requests. The existing objectstore-based design of the CTA Scheduler...
Go to contribution page -
Dimitrios Matakias (CERN), Paris Moschovakos06/02/2026, 10:35Day 1
The ATLAS Detector Control System manages over 68 TB of time-series data accumulated since 2007. This presentation describes the practical implementation and operational deployment of TimescaleDB—a PostgreSQL extension—to modernize DCS data access for the ATLAS experiment. We share our experience as PostgreSQL users and administrators implementing a production time-series database solution in...
Go to contribution page -
Teresa Lopes (Adyen)06/02/2026, 11:15Day 1
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...
Go to contribution page -
Robert Treat06/02/2026, 13:15Day 1
We have all heard about Postgres vacuum horror stories and tales of transaction wraparound disasters. Even if you've never been through one yourself, you may be concerned that you might someday experience it, or maybe you even know people who have avoided Postgres altogether due to fear of it happening to them. But it doesn't have to be this way.
In this talk, we will explore this topic...
Go to contribution page -
Álvaro Hernández06/02/2026, 14:10Day 1
Sharding enables horizontal scaling of Postgres, by logically splitting your database into several subsets ("shards"). Each shard will be a primary or, for high availability purposes, a primary-replica cluster. This allows you to scale writes horizontally, allowing Postgres to reach database sizes of multiple terabytes or even petabytes.
Sharding solutions for Postgres exist in multiple...
Go to contribution page -
Josef Machytka06/02/2026, 15:25Day 1
Talk dissects PostgreSQL’s shared buffers: the three‑layer design (buffer pool → BufferDesc headers → buf_table hash), the hit/miss/I‑O lifecycle, and how pins, per‑page LWLocks, and atomic BM_* flags coordinate page‑granular concurrency. We will trace clock‑sweep and buffer rings that prevent big scans and VACUUM from polluting the cache, then follow WAL‑before‑data through bgwriter and the...
Go to contribution page -
Ms Marion Baumgartner06/02/2026, 16:20Reserve List
In this talk, we will explore the powerful incremental backup feature introduced in PostgreSQL 17. Rather than backing up the entire database, incremental backups focus on the changes made since the last backup. This approach significantly reduces time and storage requirements compared to full backups, making incremental backups an efficient, time-saving solution for data backup...
Go to contribution page -
Maurizio De Giorgi (CERN), Markus Wanner06/02/2026, 17:05Day 1
Closing notes with sponsors review and special thanks
Go to contribution page -
Barbora Linhartova, Jan SuchanekDay 1
What happens when a stream-obsessed writer meets a data-loving elephant?
You get a fast, open, and surprisingly elegant story about modern data ingestion.This talk shows how PostgreSQL 18 can act as the central hub of an open Data Mesh, powered by Kafka and JDBC Sink connectors. We’ll explore how new features like Asynchronous I/O, JSON_TABLE, and parallel COPY dramatically boost ingest...
Go to contribution page
Choose timezone
Your profile timezone: