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
  • Konstantin Knignik
    Konstantin Knignik PostgresPro

    PostgreSQL looks very competitive with other mainstream databases on OLTP workload (execution of large number of simple queries). But on OLAP queries, requiring processing of larger volumes of data, DBMS-es oriented on analytic queries processing can provide an order of magnitude better speed. The following factors limit Postgres OLAP performance:

    • Unpacking tuple overhead (tuple_deform)
    • Interpretation overhead (Postgres executor has to interpret query execution plan)
    • Abstraction penalty (support of abstract data types)
    • Pull model overhead (operators are pulling tuples from heap page one-by-one, resulting numerous repeated accesses to the page)
    • MVCC overhead (extra per-tuple storage + visibility check cost)

    All this issues can be solved using vectorized executor, which proceed bulk of values at once. In this presentation I will show how vector operations can be implemented in Postgres as standard Postgres extension, not affecting Postgres core. The approach is based on introducing special types: tile types, which can be used instead of normal (scalar) types and implement vector operations. Postgres extension mechanism, such as UDT (user-defined type), FDW (foreign data wrappers), executor hooks are used to let users work with vectorized tables almost in the same way as with normal tables. But more than 10 times faster because of vector operations.

  • Антон Дорошкевич
    Антон Дорошкевич Infosoft

    Comparison of capabilities of PostgreSQL and MS SQL to work with 1С. What does pg_restore mean for 1С user? Results of load testing for 1C database of more than 1TB size. The story of one 1C Production: 2 years, 500+ databases 1C, 4TB of data, cascading replication.

  • Дмитрий Шитов
    Дмитрий Шитов Centre of technical projects

    What is a real cost of not paying for Windows for 1C-user? Is there life without COM? Addressing and other issues for the bunch of PostgreSQL. Scheduling disk resources. How to overcome OS CentOS crash.

All talks

Partners

PGConf.Russia 2018

Silver

Organizational

Informational

Partner