Re: [HACKERS] Relcache leak when row triggers on partitions are firedby COPY

Поиск
Список
Период
Сортировка
От Thomas Munro
Тема Re: [HACKERS] Relcache leak when row triggers on partitions are firedby COPY
Дата
Msg-id CAEepm=3Za+CVmkxzh0pZCxbTNZtPq=vDWGFVoX82-fEppb8hGw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [HACKERS] Relcache leak when row triggers on partitions are firedby COPY  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
Ответы Re: [HACKERS] Relcache leak when row triggers on partitions are firedby COPY  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
Список pgsql-hackers
Дерево обсуждения 
On Tue, May 16, 2017 at 12:32 PM, Amit Langote
<Langote_Amit_f8@lab.ntt.co.jp> wrote:
> I vote for ExecCleanupTriggerState(estate).  After your patch, there will
> be 4 places, including afterTriggerInvokeEvents(), ExecEndPlan(), and
> EvalPlanQualEnd(), that repeat the same block of code.

Ok, here's a patch like that.  The call to ExecCloseIndices() may
technically be redundant (we never opened them).

-- 
Thomas Munro
http://www.enterprisedb.com

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Вложения

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Amit Langote
Дата:
Сообщение: Re: [HACKERS] Relcache leak when row triggers on partitions are firedby COPY
Следующее
От: Masahiko Sawada
Дата:
Сообщение: Re: [HACKERS] Server Crashes if try to provide slot_name='none' atthe time of creating subscription.