X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 17E169FB3F6 for ; Thu, 31 Aug 2006 17:41:47 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 86802-02-2 for ; Thu, 31 Aug 2006 17:41:35 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id EA6129FB413 for ; Thu, 31 Aug 2006 17:37:21 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k7VKadDm023610; Thu, 31 Aug 2006 16:36:39 -0400 (EDT) To: "Sriram Dandapani" cc: pgsql-admin@postgresql.org Subject: Re: archive logs recovery In-reply-to: <6992E470F12A444BB787B5C937B9D4DF05ABC4C2@ca-mail1.cis.local> References: <6992E470F12A444BB787B5C937B9D4DF05ABC4C2@ca-mail1.cis.local> Comments: In-reply-to "Sriram Dandapani" message dated "Thu, 31 Aug 2006 13:27:02 -0700" Date: Thu, 31 Aug 2006 16:36:39 -0400 Message-ID: <23609.1157056599@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.131 tagged_above=0 required=5 tests=AWL, SPF_HELO_PASS, SPF_PASS X-Spam-Level: X-Archive-Number: 200608/366 X-Sequence-Number: 22909 "Sriram Dandapani" writes: > I have a very high traffic db with lots of table partitions. The only > reliable way to drop the partitioned tables is to prevent any > insert/select on the parent table , otherwise, the drop table locks out > the inserts, and strangely enough, the drop table command goes into a > wait state. During shutdown and restart, I switch the pg_hba.conf to > disallow client access for a brief period when the tables are dropped. You do know you can change pg_hba.conf without a restart? As for the drop going into a wait state, you might want to look around for client code that's sitting idle with an open transaction. The drop should not block for longer than whatever is your longest transaction touching that table. regards, tom lane