title

text

Pavel Tolmachev
Pavel Tolmachev Postgres Professional
: December
45 мин

Collapse in query plans. Achieve it and manage it

The more tables are involved with the query, the more difficult it is for the scheduler to choose a suitable execution plan (both time and memory usage increase). How can we "tell" the planner that it is better to connect this pair of tables first, and the rest can be connected later? What if we see that a part of our query can be improved, but the optimizer does not do this. In my presentation, I will talk about managing the order of connections. I will explain how we can influence the formation of a query plan using the standard "vanilla" PostgreSQL methods.

Слайды

Толмачев.odp

Видео

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

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

  • Alexey Borschev
    Alexey Borschev Postgres Professional
    22 мин

    NULLs in Postgres

    This presentation is about NULLs implementation in the Postgres database: - What is NULL? - How is it handled by various Postgres functions? - How are NULLs stored in the database? - Indexing of NULLs

  • Egor Rogov
    Egor Rogov Postgres Professional
    45 мин

    The Dark Side of “PostgreSQL Internals”

    A book. Typically a reader sees only the final product, printed on paper or opened on a computer screen. In this talk I invite you to take a look at the dark side of my recently published “PostgreSQL Internals” book. Come if you are curious why the author would want to write scripts, modify the PostgreSQL source code, and program pictures.

  • Nikita Malakhov
    Nikita Malakhov Postgres Professional
    Teodor Sigaev
    Teodor Sigaev Postgres Professional
    45 мин

    Big values in PostgreSQL

    A modern database should be capable of storing big values. Storing itself is not a big deal, however, operations with big values or fields are a non-trivial task. PostgreSQL has several options for storing big values, but none of them is perfect. How do we respond to this challenge? Our presentation answers this question, let's see how to store big and complex values in Postgres properly, and how operate with them.