| From: | Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
|---|---|
| To: | Stas Kelvich <s(dot)kelvich(at)postgrespro(dot)ru> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Logical replication ApplyContext bloat |
| Date: | 2017-04-20 14:01:51 |
| Message-ID: | CAFiTN-tj7m=0fR0PrXJj+3tg9ardeN+XKUNzK10g2L4h_7jAQA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Apr 20, 2017 at 7:04 PM, Stas Kelvich <s(dot)kelvich(at)postgrespro(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Petr Jelinek | 2017-04-20 14:19:29 | Re: DROP SUBSCRIPTION, query cancellations and slot handling |
| Previous Message | Petr Jelinek | 2017-04-20 13:46:35 | Re: Use sync commit for logical replication apply in TAP tests |