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

From Peter Eisentraut
Subject Re: [HACKERS] Logical replication ApplyContext bloat
Date
Msg-id d422bdc8-ff02-c171-8dff-3e1fe52bdc89@2ndquadrant.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  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
I'm not sure about some of the details.

I think it would make more sense to reset ApplyMessageContext in
apply_dispatch(), so that it is done consistently after every message
(as the name implies), not only some messages.

Also, perhaps ApplyMessageContext should be a child of
TopTransactionContext.  (You have it as a child of ApplyContext, which
is under TopMemoryContext.)

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



pgsql-hackers by date:

Previous
From: Dmitriy Sarafannikov
Date:
Subject: Re: [HACKERS] [PROPOSAL] Use SnapshotAny in get_actual_variable_range
Next
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] Logical replication ApplyContext bloat