PostgreSQL for Python Software Developers

PGConf.Russia 2021

October 25 – 26 |
Sechenov University, Moscow, Russia

What is PGConf.Russia 2021?

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 3-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

October 25 – 26, 2021 (10:00-19:00)
Moscow, Russia

Attendees

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

Main topics

PostgreSQL at the cutting edge of technology: big data, internet of things, blockchain
New features in PostgreSQL and around: PostgreSQL ecosystem development
PostgreSQL in business software applications: system architecture, migration issues and operating experience
Integration of PostgreSQL to 1C, GIS and other software application systems.

>500
participants

hybrid format

1000
minutes of networking

Selected talks

Teodor Sigaev

Postgres Professional

CTO

Talk

Why do we need 64-bit transaction IDs?

When PostgreSQL was at its formation stage, its transaction ID was chosen to be 32-bit. Back then, no one could imagine that someday we may need more than 4 billion transactions. However, ongoing technical progress and digitization pushed some Postgres instances towards their transaction ID limit. The Postgres community reacted to this with a wraparound of the transaction ID counter. However, constantly growing data volumes exposed PostgreSQL to new challenges. In my presentation, I will cover these challenges and explain how they can be solved with a 64-bit transaction ID, what the consequences will be like, why now it is a good time to implement 64x IDs, and why this hasn't been done previously.

Slides

Anton Doroshkevich

InfoSoft

Chief Information Officer

Talk

Unequal battle with "bloating" in the realities of 1C databases

Data is getting bigger, disks are getting faster, the DBMS optimizer is getting smarter, but the problem of " bloating " remains extremely relevant. I want to share my experience and approach to dealing with this effect on a large number of tables and data in them.