title

text

June 20 – 21 , 2022

PGConf.Russia 2022

Radisson Slavyanskaya Business Center, Square of Europe 2, Moscow

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
  • более
    0 участников
  • 0 докладов
  • гибридный
    формат
  • 0
    минут общения

Доклады

Архив докладов

PGConf.Russia 2022
  • Pavel Tolmachev
    Pavel Tolmachev Postgres Professional
    45 мин

    Коллапс в планах запросов. Достигаем и управляем

    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.

  • Vadim Yatsenko
    Vadim Yatsenko Tantor Lab
    45 мин

    Autovacuum. Вредные советы

    PostgreSQL has a number of peculiarities that you need to take into account not only while maintaining your database but also when designing your database schema. Experienced PostgreSQL are well aware of vacuuming process. On the web one can find tons of materials covering its internals, configurations and monitoring. Many valuable talks about vacuum were given at numerous conferences. However, we still face the common wraparound problem when the maximum possible number of transactions (xid) is reached. It happens even on databases that are relatively small in size. In my presentation, I will share a customer case that looks interesting to me. A chain of mistakes made at different stages of the database's life cycle once caused a disaster. The database fully stopped for one week, we detected a wraparound and spotted corrupted blocks. Maintenance was problematical, and we spent sleepless nights in search of a solution. We managed to achieve a local win as we finally restored the database, but it's not the end of this story, which makes it even more interesting.

  • Иван Чувашов
    Иван Чувашов ООО Calltouch
    22 мин

    Повреждение данных PostgreSQL на жестком диске. Что делать и как исправить?

    Every DBMS stores its data on a hard disc, so you may face a situation when your data on disc gets corrupted. This can happen due to a controller failure, logical or physical data corruption; there are also other reasons. If it is just the index file that gets corrupted, the index recreation command will enable you to restore data consistency in your DBMS. If a table file or a file of a system section gets corrupted, data restore is impossible. In this case, you need to invent workarounds. You can try to restore this data from backup files, copy it from the corrupted table, or find another way to solve this problem. In this talk, we'll tackle several cases of data corruption on disc and describe the options for restoring the data from the corrupted tables.

  • Denis Sukhovei
    Denis Sukhovei Аладдин Р.Д.
    Alexey Sabanov
    Alexey Sabanov АО "Аладдин Р.Д."
    45 мин

    Криптографическая защита информации с помощью "Крипто БД" или как достичь технологического суверенитета информационной системы

    The myths and misconceptions of software import substitution. The acute threat of non-working DBMS servers. The basic plans for import substitution and problems of the transition period. DBMS data protection and the image of an ideal protection system. Crypto BD is the cryptographic data protection system. How does it work?

Все доклады

Партнёры

PGConf.Russia 2022

Informational

Partner