Ilya Kosmodemiansky

If you ever wanted to find out what can be configured in postgresql.conf, you can easily find it in the official Postgres documentation. So, all you need to do is read it, yes, all of it, and you will have a perfectly configured database.

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.

This practical tutorial will guide you through the complete process of PostgreSQL installation, providing you with the necessary skills to operate PostgreSQL in a realistic production environment. We will begin by installing and configuring PostgreSQL on Linux.

This talk is prepared as a bunch of slides, where each slide describes a really bad way people can screw up their PostgreSQL database and provides a weight - how frequently I saw that kind of problem.

In this tutorial, we will go through the typical day-to-day of PostgreSQL DBA, which includes following sections: Each section will include instructions, explanations of how they work in real life and important additional details that are normally learned the hard way. The purpose of this tutorial is to give a compact and useful guidance on where to start as PostgreSQL DBA without overwhelming...

Input-output performance problems are on every day agenda for DBAs since the databases exist. Volume of data grows rapidly and you need to get your data fast from the disk and moreover - fast to the disk.

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.

PostgreSQL database on Linux operating system has been and remains the industry default open-source ecosystem for many years.This setup has proven itself as a very reliable combo, and with correct planning, appropriate configuration and proper everyday operation performs really well.In this training, I will talk participants though the full installation and configuration circle of the...

We all remember the day we realized a database transaction is a slightly more fundamental concept than we thought. It is not just BEGIN/COMMIT/ROLLBACK syntax sugar in our programs that of course makes them more complex and slows them down.

This talk is prepared as a bunch of slides, where each slide describes a really bad way people can screw up their PostgreSQL database and provides a weight - how frequently I saw that kind of problem.

Sooner or later you run into situation, when it is no more possible to improve performance of your beloved database-interacting project only by changing some postgresql.conf settings.

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.

If you ever wanted to find out what can be configured in postgresql.conf, you can easily find it in the official Postgres documentation. So, all you need to do is read it, yes, all of it, and you will have a perfectly configured database.

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.

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.