title

text

April 03 – 04 , 2023

PGConf.Russia 2023

  • more than
    0 participants
  • 0 speakers
  • 0
    minutes of conversation
  • 44 talks
  • hybrid
    format

Talks

Talks archive

PGConf.Russia 2023
  • Andrey Zubkov
    Andrey Zubkov PostgresPro

    In this talk I’ll show some new abilities in postgres observability. There will be Graphana visualization of pg_profile/pgpro_pwr data, manual highlighting of interesting objects in pg_profile/pgpro_pwr reports, further development of extended vacuum statistics in PostgresPro releases and a new session and query tracing technique in pgpro_stats extension

  • Vigneshwaran C
    Vigneshwaran C FUJITSU INDIA

    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

  • Christopher Travers
    Christopher Travers Independent Community Member

    With the rise of NoSQL databases, a number of falsehoods have flourished regarding how to choose a database engine. This talk focuses specifically on Redis and PostgreSQL, and why one might choose one or the other.

    At small scales, we can often get by thinking of database servers as black boxes, but as we scale, the internals and architecture become more and more important. This talk focuses on behavior of these systems at scale and under load.

    In this presentation you will learn:

    • How Redis and PostgreSQL differ architecturally
    • How differences in architecture affect scalability and performance
    • Cases here Redis is the clear winner
    • Cases where PostgreSQL is the clear winner

    Additionally, some notes will be offered in terms of where PostgreSQL can improve in to compete with the sorts of workloads that generally favor Redis.

  • Pavel Tolmachev
    Pavel Tolmachev PostgresPro

    -----------------------------------------------------------QUERY PLAN--------------------------------------------------------------
    Hash Join
      Hash Cond: (Subject = GEQO)
      -> Hash Join
            Hash Cond: (**Optimizer task = choose the best query execution plan**)
            -> Seq Scan on **The number of potential plans grows exponentially as the number of tables in a query increases**
            -> Hash
                  -> Seq Scan on **PostgreSQL solves this problem by using the genetic optimizer (GEQO)**
      -> Hash
            -> Seq Scan on **Topics of the report:**
                  Filter: (**(What is GEQO)** AND **(Pros and cons)** AND **(How it works)**)
    (10 rows)
    

All talks

Partners

PGConf.Russia 2023

Golden

Informational

Partner