Ilya Kosmodemiansky

Even an experienced PostgreSQL DBA can not always say that upgrading between major versions of Postgres is an easy task, especially if there are some special requirements, such as downtime limitations or if something goes wrong. For less experienced DBAs anything more complex than dump/restore can be frustrating.

In this talk I will describe why we need a special procedure to upgrade between major versions, how that can be achieved and what sort of problems can occur. I will review all possible ways to upgrade your cluster from classical pg_upgrade to old-school slony or modern methods like logical replication. For all approaches, I will give a brief explanation how it works (limited by the scope of this talk of course), examples how to perform upgrade and some advice on potentially problematic steps. Besides I will touch upon such topics as integration of upgrade tools and procedures with other software — connection brokers, operating system package managers, automation tools, etc. This talk would not be complete if I do not cover cases when something goes wrong and how to deal with such cases.

Input-output performance problems are on every day agenda for DBAs since databases exist. In Linux - probably the most popular operating system for databases now - there is a major overhaul of the IO stack for last several years. In this talk i will review what is going on there, why the IO stack needed an urgent improvement and what all those brand new NVMe driver and blk-mq layer improvements mean for databases, and database people. As a useful takeaway, I will provide a checklist of PostgreSQL and Linux settings to maximize IO performance with the new kernels.

Input-output performance problems are on every day agenda for DBAs since databases exist. In Linux - probably the most popular operating system for databases now - there is a major overhaul of the IO stack for last several years. In this talk i will review what is going on there, why the IO stack needed an urgent improvement and what all those brand new NVMe driver and blk-mq layer improvements mean for databases, and database people. As a useful takeaway, I will provide a checklist of PostgreSQL and Linux settings to maximize IO performance with the new kernels.