PGConf.Russia 2025

Two years ago, I spoke about data retrieval queries, where the LINQ to DB library offers almost limitless possibilities.

This talk is about data modification operations. LINQ to DB allows you to execute UPDATE + JOIN queries, INSERT FROM SELECT, supports the MERGE operator, row-level locking with SELECT FOR UPDATE, temporary table creation, and features a fast data insertion mechanism.

I will also discuss the linq2db. EntityFrameworkCore project — a solution for those who aren’t ready to leave EF Core but still want the capabilities of LINQ to DB. I’ll share our experience implementing LINQ to DB in a large-scale project.

I’ll talk about the challenges you’ll face if you decide to implement a new TableAM. What to choose: Generic XLog or Custom RMGR? Why use a Custom SMGR? How to integrate PostgreSQL allocators into third-party libraries, even if they don't officially support it? What’s missing for a columnar engine (including vectorization and late materialization), and how can we work around those limitations?

In the second part, I’ll dive into the internals of pgpro_tam — a new native table engine for OLAP that supports standard data formats, various SMGRs, and, if needed, third-party schedulers and execution engines, all while adhering to ACID principles. This is designed to achieve the fastest analytics on PostgreSQL (not just plugging in DuckDB).

Covering all the key changes in PostgreSQL 18 during this talk would be quite a challenge — especially since the code freeze is set to happen just a week after the presentation. However, I’ll focus on what has already been finalized.

There are plenty of exciting updates in performance, monitoring, vacuuming (of course!), and beyond. As always, this talk is based on a series of articles reviewing the commit fests for PostgreSQL 18, published on Postgres Professional’s corporate blog on Habr.

In this talk, I will challenge architectural stereotypes about the impossibility of communication with external systems directly from a DBMS. PostgreSQL offers vast communication capabilities; you just need to know which extensions to use.

And when extensions aren't enough, you can create your own. For the Luxms BI project, we needed communication with NATS, so we developed our own extension in Rust. I’ll share the GitHub link and my experience of developing PostgreSQL extensions in Rust during this talk.