Виктор Еремченко
Виктор Еремченко Miro
15:45 04 February
45 мин

Fault-tolerance cluster PostgreSQL + Patroni

I will speak about our experience in solving the fault-tolerance problem for PostgreSQL, which options we reviewed and how we chose Patroni.

I will cover solution testing, quick implementation to the production and issues we faced as well as the way we solved them.



Другие доклады

  • Alexey Fadeev
    Alexey Fadeev Sibedge
    22 мин

    GraphQL backend on PostgreSQL with plv8.

    Recently, I was working on a project where graphQL was used for sending requests to its .NET Core backend, but this was not a good idea. The point is, a graphQL query is a hierarchical structure with a dynamic set of fields. It’s difficult to perform such requests via a statically-typed programming language and a relational database as suggested by the tools available. So, I came up with the idea of using the plv8 extension and perform graphQL queries right on the database side. It took me about two hours to develop a working prototype that could perform the same queries as the software under development for more than one month! Then various improvements have been made and I want to introduce them all. If you are thinking of using graphQL instead of REST, my speech could be most useful and could help you to save a lot of time.

  • Vasiliy Puchkov
    Vasiliy Puchkov ООО
    45 мин

    PostgreSQL Database operational experience in enterprise-level network.

    · Enterprise network traits, known problems and workarounds.

    · Year-long background of maintaining 24x7 1C + PostgreSQL systems

    · Pros and cons in comparison with MS SQL from DBA point

    · Stories of 1C systems migration from MS SQL to PostgreSQL

  • Andrey Zubkov
    Andrey Zubkov ООО "Пармалогика"
    45 мин

    An easy tool for historical workload analysis in Postgres database - pg_profile

    Any DBA needs some kind of tool for historical workload analyse. Assume once at morning your monitoring team will report of sudden performance degradation at 2-3 a.m., and now you need to investigate this issue. What activities was most resource consuming within that hour? There are several tools for solving this problem, and I'll talk about one very easy and convenient tool - pg_profile. It need only a postgres database and a cron-like tool to run, and it will generate a workload profile report for your database as you need it. Ths report will be a good start point for further investigation.