title

text

February 05 – 07 , 2018

PGConf.Russia 2018

PGConf.Russia is a leading Russian PostgreSQL international conference, annually taking together more than 500 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.

Thems

  • 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.
  • more than
    0 participants
  • 0 speakers
  • 0
    minutes of conversation
  • 54 talks
  • offline
    format

Talks

Talks archive

PGConf.Russia 2018
  • Nikolay Ryzhikov
    Nikolay Ryzhikov Health Samurai

    If you honestly evaluate most of our business applications, you will see that they first collect and import the data into a database and then send the same data in the opposite direction.

    What if we don't build an ORM wall between the application and the database, but try using the symbiosis of their strong points and special features instead?

    I will tell you how we use PostgreSQL and Clojure for building data-intensive medical applications. We will cover the following topics:

    • functional relational programming
    • jsonb for modeling complex data domains
    • functional indexes and json-knife extension for jsonb search
    • graphql implementation on PostgreSQL
    • logical replication for building reactive integrations
    • asynchronous JDBC-free connector to PostgreSQL on netty

  • Dmitriy Sarafannikov
    Dmitriy Sarafannikov Yandex

    It's not a secret for anyone that statistics can not be transferred with a major upgrade. For small and not heavily loaded databases this is not a problem, you can quickly collect new statistics. But we have databases with a volume of about 5TB and a load of about 100k rps, for which it became a big problem: taking off without statistics, the replicas could not even replay WAL. In my report I'll tell you what tricks we went to upgrade these databases with requirements of 100% read only availability, about what mistakes were made, and about how these errors were painfully corrected. The result of these errors was the extension called "pg_dirty_hands", in which we will collect various hacks, which can be last resort to repair data corruption.

  • Alex Lustin
    Alex Lustin SilverBulleters, LLC

    I would like to share experience in runing PostgreSQL in dockerized environments, describe the specific issues and tools you will need to solve them.

    • Which problems could be solved by Docker for PostgreSQL, e.g. PostgreSQLPro.9.6
    • Work of IT team with Docker in development, testing and production environments
      • Using image repository and build servers for image testing
    • Issues in production environment:
      • With network activity
      • With persistent repositories for Docker
      • With additional services
      • With load balancing and fail-safety
    • Running PostgreSQL-base applications, such as:
      • SonarQube
      • Gitlab
      • 1С platform

All talks

Partners

PGConf.Russia 2018

Silver

Organizational

Informational

Partner