Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 0500C9FB210 for ; Fri, 29 Sep 2006 18:38:13 -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 27870-02 for ; Fri, 29 Sep 2006 18:38:10 -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 D5C3C9FA5F7 for ; Fri, 29 Sep 2006 18:38:09 -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 k8TLc74d003832; Fri, 29 Sep 2006 17:38:08 -0400 (EDT) To: "Sriram Dandapani" cc: "Matthew T. O'Connor" , pgsql-admin@postgresql.org Subject: Re: autovacuum ignore tables In-reply-to: <6992E470F12A444BB787B5C937B9D4DF060E5C05@ca-mail1.cis.local> References: <6992E470F12A444BB787B5C937B9D4DF060E5C05@ca-mail1.cis.local> Comments: In-reply-to "Sriram Dandapani" message dated "Fri, 29 Sep 2006 11:21:50 -0700" Date: Fri, 29 Sep 2006 17:38:07 -0400 Message-ID: <3831.1159565887@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.095 tagged_above=0 required=5 tests=AWL, SPF_HELO_PASS, SPF_PASS X-Spam-Level: X-Archive-Number: 200609/381 X-Sequence-Number: 23295 "Sriram Dandapani" writes: > Real question is: Why do the INSERTS go into wait state as soon as the > lock table statement is issued on the parent? If you were just inserting directly into other child tables, a lock on either the parent or the target child table shouldn't affect them. I wonder if you are using conditional rules to redirect the inserts, and the rules include a reference to the target table? If that's the case, you really need to drop the relevant rule before you remove the child table, anyway. regards, tom lane