Gülçin Yıldırım Jelinek

PostgreSQL is a general-purpose transactional engine. Its row store, WAL, MVCC, vacuum and constraint enforcement are tuned for OLTP and that same machinery carries a cost for append-heavy telemetry, large analytical scans or datasets that live in object storage.

PostgreSQL now runs everywhere, on-prem, cloud-managed, on Kubernetes. Each deployment model comes with its own monitoring stack, its own blind spots, and its own trade-offs.

oin for an event focused on running PostgreSQL in cloud native (and cloud neutral) environments. We will explore the current landscape of Postgres operators, share best practices, discuss challenges, and dive deeper into production stories from both users and maintainers.

PostgreSQL 19 ships a focused set of monitoring improvements that, taken together, close several long-standing observability gaps. This talk walks through the changes that matter most for DBAs, platform engineers and tooling authors.

PostgreSQL 19 ships a focused set of monitoring improvements that, taken together, close several long-standing observability gaps. This talk walks through the changes that matter most for DBAs, platform engineers and tooling authors.

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.

Short abstract Understanding table-level locks in Postgres is a quite useful skill as almost all DDL operations require acquiring one of the different types of table-level locks on the object being manipulated.

Understanding table-level locks in Postgres is a quite useful skill as almost all DDL operations require acquiring one of the different types of table-level locks on the object being manipulated.

This talks explains locking mechanisms (MVCC, lock queue) in PostgreSQL, focusing on table-level locks that are acquired by Data Definition Language(DDL) operations.

Short abstract: Understanding table-level locks in Postgres is a quite useful skill as almost all DDL operations require acquiring one of the different types of table-level locks on the object being manipulated.

Short abstract Understanding table-level locks in Postgres is a quite useful skill as almost all DDL operations require acquiring one of the different types of table-level locks on the object being manipulated. If not managed well, schema changes can result in downtime.