Re: Dropping a partitioned table takes too long

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, 高增琦 <pgf00a(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Dropping a partitioned table takes too long
Date: 2017-04-28 18:03:29
Message-ID: CA+TgmoY98qeG1rpHD3ccoawerYWuRp6A8NPPPMHqT9Tcyevusg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Apr 26, 2017 at 12:21 PM, Peter Eisentraut
<peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
> On 4/26/17 12:15, Robert Haas wrote:
>> On Tue, Apr 25, 2017 at 10:05 PM, Amit Langote
>> <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> wrote:
>>>> The attached patch try to replace 'heap_open' with 'LockRelationOid' when
>>>> locking parent table.
>>>> It improved dropping a table with 7000 partitions.
>>>
>>> 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.
>
> Seems quite reasonable.

OK, done.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2017-04-28 18:08:05 Re: Dropping a partitioned table takes too long
Previous Message Robert Haas 2017-04-28 17:53:06 Re: Crash when partition column specified twice