title

text

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
  • more than
    0 participants
  • 0 speakers
  • 0
    minutes of conversation
  • 35 talks
  • hybrid
    format

Talks

Talks archive

PGConf.Russia 2022
  • Alexander Kukushkin
    Alexander Kukushkin Zalando SE

    Logical decoding and replication slots introduced in PostgreSQL 9.4 (released in 2014) created a solid foundation for implementing built-in core logical replication in version 10 (released in 2017). Unfortunately, there are a few limitations that make logical replication not very useful in real-world scenarios. Logical decoding currently isn’t supported on the standby server, and PostgreSQL allows creating logical replication slots only on the primary server. Or in other words, logical slots are lost on failover/switchover.

    Postgres hackers made many attempts to address the problem, and most of them resulted in not too much success. Although, there is one little function introduced in PostgreSQL 11 that made it possible to implement failover of logical replication slots externally.

    In my talk I will tell a story of how Patroni solves the problem of logical replication slots failover without using invasive third-party extensions, dig down into some of the Postgres internals in order to prove why this approach is safe, and finally, we will discuss limitations and potential downsides of this solution.

  • Vitaliy Rann
    Vitaliy Rann VK Cloud Solutions

    A cloud provider operates with lots of hardware resources and network entities. It's one thing when a company runs dozens of Postgres Pro instances in an isolated loop for internal tasks. And it’s quite a different story when a cloud provider renders services to B2B users and maintains solutions for 500+ large companies.

    Vitaliy will tell how the VK Cloud Solutions cloud provider currently employs Managed Postgres Pro. He will also demonstrate the solution's architecture and cover the challenges faced while creating the Postgres Pro solution in our cloud.

  • Ivan Frolkov
    Ivan Frolkov PostgresPro

    During my career, I've seen a lot of code, and very often I faced inaccuracies in handling dates and times. Sometimes the parties got discrepancies in the monthly reports due to such inaccuracies; or daily reports were different for Moscow and SFO, etc. I wouldn't call it a serious problem, but it's annoying and time-consuming. In all cases, such issues occur because of neglectful handling of dates and times. In my presentation, I will discuss how we can avoid it.

All talks

Partners

PGConf.Russia 2022

Informational

Partner