Re: [HACKERS] Logical replication ApplyContext bloat - Mailing list pgsql-hackers

From Dilip Kumar
Subject Re: [HACKERS] Logical replication ApplyContext bloat
Date
Msg-id CAFiTN-tj7m=0fR0PrXJj+3tg9ardeN+XKUNzK10g2L4h_7jAQA@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Logical replication ApplyContext bloat  (Stas Kelvich <s.kelvich@postgrespro.ru>)
Responses Re: [HACKERS] Logical replication ApplyContext bloat  (Stas Kelvich <s.kelvich@postgrespro.ru>)
List pgsql-hackers
On Thu, Apr 20, 2017 at 7:04 PM, Stas Kelvich <s.kelvich@postgrespro.ru> wrote:
> Thanks for noting.
>
> Added short description of ApplyContext and ApplyMessageContext to README.


+ApplyContext --- permanent during whole lifetime of apply worker. It is
+possible to use TopMemoryContext here as well, but for simplicity of
memory usage
+analysys we spin up different context.


Typo

/analysys/analysis


-- 
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Petr Jelinek
Date:
Subject: Re: [HACKERS] Use sync commit for logical replication apply in TAPtests
Next
From: Petr Jelinek
Date:
Subject: Re: [HACKERS] DROP SUBSCRIPTION, query cancellations and slothandling