Re: [HACKERS] Logical replication ApplyContext bloat

Поиск
Список
Период
Сортировка
Искать
От
Simon Riggs
Тема
Re: [HACKERS] Logical replication ApplyContext bloat
Дата
Msg-id
CANP8+jJrSdOfijzPyrKvXYGqr-7LovHyTW7BpD1=pam9sMdtwg@mail.gmail.com
Ответ на
Список
Дерево обсуждения
[HACKERS] Logical replication ApplyContext bloat Stas Kelvich <s.kelvich@postgrespro.ru>
Re: [HACKERS] Logical replication ApplyContext bloat Petr Jelinek <petr.jelinek@2ndquadrant.com>
Re: [HACKERS] Logical replication ApplyContext bloat Stas Kelvich <s.kelvich@postgrespro.ru>
Re: [HACKERS] Logical replication ApplyContext bloat Petr Jelinek <petr.jelinek@2ndquadrant.com>
Re: [HACKERS] Logical replication ApplyContext bloat Simon Riggs <simon@2ndquadrant.com>
Re: [HACKERS] Logical replication ApplyContext bloat Stas Kelvich <s.kelvich@postgrespro.ru>
Re: [HACKERS] Logical replication ApplyContext bloat Petr Jelinek <petr.jelinek@2ndquadrant.com>
Re: [HACKERS] Logical replication ApplyContext bloat Stas Kelvich <s.kelvich@postgrespro.ru>
Re: [HACKERS] Logical replication ApplyContext bloat Alvaro Herrera <alvherre@2ndquadrant.com>
Re: [HACKERS] Logical replication ApplyContext bloat Stas Kelvich <s.kelvich@postgrespro.ru>
Re: [HACKERS] Logical replication ApplyContext bloat Dilip Kumar <dilipbalaut@gmail.com>
Re: [HACKERS] Logical replication ApplyContext bloat Stas Kelvich <s.kelvich@postgrespro.ru>
Re: [HACKERS] Logical replication ApplyContext bloat Noah Misch <noah@leadboat.com>
Re: [HACKERS] Logical replication ApplyContext bloat Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: [HACKERS] Logical replication ApplyContext bloat Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: [HACKERS] Logical replication ApplyContext bloat Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: [HACKERS] Logical replication ApplyContext bloat Stas Kelvich <s.kelvich@postgrespro.ru>
On 19 April 2017 at 11:24, Petr Jelinek  wrote:

> I'd still like you to add comment to the ApplyContext saying that it's
> cleaned after handling each message so nothing that needs to survive for
> example whole transaction can be allocated in it as that's not very well
> visible IMHO (and I know I will forget about it when writing next patch
> in that area).

It would be better to invent the contexts we want now, so we get the
architecture right for future work. Otherwise we have problems with
"can't backpatch this fix because that infrastructure doesn't exist in
PG10" in a couple of years.

So I suggest we have

ApplyMessageContext - cleaned after every message
ApplyTransactionContext - cleaned at EOXact
ApplyContext - persistent

-- 
Simon Riggs                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


В списке pgsql-hackers по дате отправления
От: Petr Jelinek
Дата:
От: Stas Kelvich
Дата:
FAQ