Received: from magus.postgresql.org ([87.238.57.229]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TGFzz-00052o-QG for pgsql-admin@postgresql.org; Mon, 24 Sep 2012 21:15:27 +0000 Received: from cerberus.pinpointresearch.com ([66.7.238.130] helo=polaris.pinpointresearch.com) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TGFzx-0006tE-Of for pgsql-admin@postgresql.org; Mon, 24 Sep 2012 21:15:27 +0000 Received: from [192.168.1.179] (betelgeuse.pinpointresearch.com [192.168.1.179]) by polaris.pinpointresearch.com (Postfix) with ESMTP id 28CC0E00EC84; Mon, 24 Sep 2012 14:15:23 -0700 (PDT) Message-ID: <5060CD6B.4010404@pinpointresearch.com> Date: Mon, 24 Sep 2012 14:15:23 -0700 From: Steve Crawford User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: Evan Walter CC: pgsql-admin@postgresql.org Subject: Re: dropping a large table is taking a very long time (about 2 hours so far) References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.7 (--) X-Archive-Number: 201209/140 X-Sequence-Number: 40081 On 09/24/2012 02:10 PM, Evan Walter wrote: > There were probaby about 5 million records in the table. I do not > believe there were any foreign keys to the table The drop table has > been going for over 2 hours. Is that normal? I'd check for locks from other transactions preventing the drop. One possibility is a running backup. Cheers, Steve