title

text

Vigneshwaran C
Vigneshwaran C FUJITSU CONSULTING INDIA
12:50 04 April
45 мин

Logical replication internals

The following topics will be covered as part of the presentation:

  • Architecture of logical replication
  • Publisher introduction
  • Subscriber introduction
  • Data syncronization introduction
  • Logical decoding
  • Replication slot
  • output plugin

Слайды

PostgreSQL_Internals_of_logical_replication_2023_PGCONF_Russia.pptx

Видео

Видео доступно участникам мероприятия, выполнившим вход в личный кабинет

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

  • Leonid Churikov
    Leonid Churikov СёрчИнформ
    22 мин

    Building the protection system based on Postgres DBMS

    Why would you need the domestic DBMS? 1. Because of law requirements: only domestic DBMSes are appropriate for data protection. 2. In terms of formalization: currently, it is impossible to purchase MS in Russia legally. 3. In terms of pricing: the licensing mechanism of foreign DBMS systems significantly increases the expenditures on protection. 4. In terms of performance: it depends on the optimization of information protection tools, which are currently developed for domestic DBMS systems (in order to reveal why you may refer to the first paragraph). 5. In terms of practice: by the end of last year we’ve finished transition to the domestic databases and everything works smoothly. What else does an information security officer need?

  • P
    Pavel Luzanov Postgres Professional
    45 мин

    PostgreSQL 16: at the finish line

    April 8, 2023 is the expected feature freeze date for PostgreSQL 16.

    Some of the new features are already known, particularly, we can expect interesting changes related to security and logical replication. However, announcing all interesting patches before the end of the March CommitFest is impossible. Based on the experience of previous releases, we can assume that the most interesting patches will be committed during late March and early April..

    That's why the contents of this talk will remain unknown till the very last moment, the author of this talk will also discover it in due time.

  • Pavel Konotopov
    Pavel Konotopov inCountry
    45 мин

    Five shades of sharding

    The importance of sharding is now colossal. The size of today's databases exceeds 100 terabytes, scaling up vertically, and adding replicas containing a complete physical copy of the database is becoming difficult, especially when computational resources are scarce. Database sharding is a way to scale horizontally by partitioning data between compute nodes that are independent of each other.

    In the PostgreSQL world, there are well-known scaling tools - CitusDB, and Greenplum - as well as new generation solutions - Cockroach DB, Yugabyte DB, SPQR, and Shardman.

    In this talk, we will discuss the difference between these implementations, the advantages, and disadvantages of these solutions, examine the current state of implementation of sharding in vanilla PostgreSQL, and also touch on another important topic - providing data integrity and consistency guarantees across a distributed cluster.

  • Максим Милютин
    Максим Милютин Wildberries
    45 мин

    Analytical open-source solutions based on PostgreSQL

    Historically PostgreSQL was intended to transactional OLTP workload. This thesis is confirmed by row-based kind of storage and impossibility (or some complication) in building distributed engine of query execution based on MPP principles. However, due to extensibility of PostgreSQL core (first of all, by using of pluggable access methods) and tolerant license policy similar to BSD there were appeared new different forks and extensions allowing effective processing of big data in analytical manner.

    In current talk I'm going to review the PostgreSQL fork called Greenplum and Citus and TimescaleDB extensions from system developer's perspective by comparing their common analytical engine features: column storage, data compression, distributed query execution and so on. The results of such overview will be helpful to database architects seeking PostgreSQL-based DBMS for analytical workload.