Re: [HACKERS] Dropping a partitioned table takes too long - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] Dropping a partitioned table takes too long
Date
Msg-id 6221.1493223733@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] Dropping a partitioned table takes too long  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: [HACKERS] Dropping a partitioned table takes too long
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Tue, Apr 25, 2017 at 10:05 PM, Amit Langote
> <Langote_Amit_f8@lab.ntt.co.jp> wrote:
>> Your patch seems to be a much better solution to the problem, thanks.

> Does anyone wish to object to this patch as untimely?

> If not, I'll commit it.

It's certainly not untimely to address such problems.  What I'm wondering
is if we should commit both patches.  Avoiding an unnecessary heap_open
is certainly a good thing, but it seems like the memory leak addressed
by the first patch might still be of concern in other scenarios.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] Dropping a partitioned table takes too long
Next
From: Fujii Masao
Date:
Subject: Re: [HACKERS] some review comments on logical rep code