Postgres Pro
Downloads
Home   >   mailing lists

Re: [HACKERS] Relcache leak when row triggers on partitions are firedby COPY - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: [HACKERS] Relcache leak when row triggers on partitions are firedby COPY
Date
Msg-id CAEepm=3Za+CVmkxzh0pZCxbTNZtPq=vDWGFVoX82-fEppb8hGw@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Relcache leak when row triggers on partitions are firedby COPY  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
Responses Re: [HACKERS] Relcache leak when row triggers on partitions are firedby COPY  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
List pgsql-hackers
Tree view 
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
Attachment

pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: [HACKERS] Relcache leak when row triggers on partitions are firedby COPY
Next
From: Masahiko Sawada
Date:
Subject: Re: [HACKERS] Server Crashes if try to provide slot_name='none' atthe time of creating subscription.