Speeding up databases using non-traditional methods

PGConf.Russia 2022

June 20 – 21 |
Radisson Slavyanskaya Business Center, Square of Europe 2, Moscow

What is PGConf.Russia 2022?

About

PGConf.Russia is a leading Russian PostgreSQL international conference, annually taking together more than 700 PostgreSQL professionals from Russia and other countries — core and software developers, DBAs and IT-managers. The 2-day program includes training workshops presented by leading PostgreSQL experts, more than 40 talks, panel discussions and a lightning talk session.

i

When and Where

June 20 – 21, 2022 (10:00-19:00)
Radisson Slavyanskaya Business Center, Square of Europe 2, Moscow

Attendees

PostgreSQL DBAs
PostgreSQL core and extension developers
Application developers
System architects
IT-managers
Database migration engineers and managers.

Main topics

PostgreSQL technology frontiers for highest workloads, huge databases, mission-critical applications
PostgreSQL scalability for transactional and analytical workloads
New features in PostgreSQL and around: PostgreSQL and its ecosystem development
PostgreSQL for business software applications: system architecture, migration issues and operating experience
PostgreSQL specific features and their applications: JSON(b), (geo)Spatial data, Full text search

>500
participants

hybrid format

1000
minutes of networking

Selected talks

Andrey Zubkov

Postgres Professional

Senior DBA

Talk

Do you want to know what VACUUM has done?

This talk is about our work on detailed vacuum workload statistics collection by the statistics collector and about problem solutions and benefits it can provide.

Slides

Pavel Tolmachev

Postgres Professional

Education Department Specialist

Talk

Collapse in query plans. Achieve it and manage it

The more tables are involved with the query, the more difficult it is for the scheduler to choose a suitable execution plan (both time and memory usage increase). How can we "tell" the planner that it is better to connect this pair of tables first, and the rest can be connected later? What if we see that a part of our query can be improved, but the optimizer does not do this. In my presentation, I will talk about managing the order of connections. I will explain how we can influence the formation of a query plan using the standard "vanilla" PostgreSQL methods.