title

text

March 15 – 17 , 2017

Postrelease

  • more than
    0 participants
  • 0 speakers
  • 0
    minutes of conversation
  • 63 talks
  • offline
    format

Talks

Talks archive

PgConf.Russia 2017
  • Michael Shurutov
    Michael Shurutov Postgres Professional

    1. What is an autonomous transaction?
    2. An overview of autonomous transactions in "big" DBMS: Oracle.
    3. Autonomous transaction logic in Postgres Pro.
    4. An overview of emulation methods for autonomous transactions in PostgreSQL.
    5. Comparing performance of the built-in Postgres Pro autonomous transaction mechanism and PostgreSQL emulation methods.

    VIDEO

  • Sergey Mirvoda
    Sergey Mirvoda Octonica, UrFU

    Experience we've got after 5 years of developing, deploying and improving BI system http://colibri365.ru used in government. I would talk about government IT reality and our way over it. Postgres performance improvements, using of latest features, overwriting of user generated queries to help query optimizer and other tweaks and hacks to tackle limited hardware problems. These lead us to number of computer science papers and (now committed) patches to Postgres (see Andrey Borodin talks for details).

    VIDEO

  • Nicholas Sivko
    Nicholas Sivko okmeter.io

    It often happens that you already have PosgtreSQL in production, but you don’t have a DBA. To demystify the PostgreSQL database, I’ll tell you how to troubleshoot various problems while working with PosgtreSQL. We will try to understand how to answer "routine" questions of a typical system administrator: - Is everything OK with the database? - What consumes DB server resources? - What to optimize first to reduce resource consumption?

    VIDEO

  • Mikhail Tyurin
    Mikhail Tyurin Independent entrepreneur in the field of data technology and predictive analytics

    < Query failed: ERROR: deadlock detected
    < DETAIL: Process 17371 waits for ShareLock on transaction 102733872; Blocked by process.
    < Process 10414 waits for ShareLock on transaction 102733874; Blocked by process 17371.
    

    Such "unpleasant" messages from the server can seriously puzzle the developer. When working with locks, in particular, with transactions in general, it is necessary to take into account the features of the implementation of client libraries, which can cause the above exception.

    In the short talk, the mechanics of the interaction of locks will be explained, main attention being paid to causes of deadlocks. References to the relevant documentation pages will be given. A technique of "bypassing" this problem of concurrent data access will be described and illustrated with some generalized examples from practice are shown. The talk will be interesting to database developers and administrators as well as the client-side application developers.

All talks