June 20 – 21 , 2022
PGConf.Russia 2022
PGConf.Russia 2022
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.
Thems
- 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
Talks
Talks archive
-
Mikhail Tsvetkov экспертAs opposed to in-memory DBMSs, traditional disc database management systems have an inherent physical limitation. It's their storage system which is by several orders of magnitude slower than CPU operation memory, even in the case of All-Flash NVM. It becomes especially critical for the development of business analytics apps and OLAP scenarios on disc DBMS. We will consider a number how-tos for improving the performance of traditional DBMSs, and then offer a new storage-centric approach to hardware-based speed-up for disc DBMSs.
-
Dmitry Vasilyev PostgresProMy talk covers PostgreSQL infrastructure in Ozon: - how do we tune virtual machines (KVM); - which version control system we have created; - which drivers we make and how it relates to fault tolerance and load balancing; - how do we make "hot" upgrades for the parameters of our virtual machines.
-
Alexey Borschev PostgresProThis presentation is about NULLs implementation in the Postgres database: - What is NULL? - How is it handled by various Postgres functions? - How are NULLs stored in the database? - Indexing of NULLs
-
Pavel Tolmachev PostgresProThe 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.
Photos
Photo archive