Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 95DDD9FBF73 for ; Thu, 17 May 2007 10:42:58 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 28768-09 for ; Thu, 17 May 2007 10:42:49 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 239CE9FB703 for ; Thu, 17 May 2007 10:42:55 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l4HDghdN023182; Thu, 17 May 2007 09:42:43 -0400 (EDT) To: Raf cc: pgsql-admin@postgresql.org Subject: Re: Manual trigger removal [WAS] Flushing Postgres Function Cache In-reply-to: <20070517135952.F69332@joshua.dreamthought.com> References: <20070517092853.R69332@joshua.dreamthought.com> <20070517122322.V69332@joshua.dreamthought.com> <20070517131522.T69332@joshua.dreamthought.com> <20070517135952.F69332@joshua.dreamthought.com> Comments: In-reply-to Raf message dated "Thu, 17 May 2007 14:02:59 +0100" Date: Thu, 17 May 2007 09:42:43 -0400 Message-ID: <23181.1179409363@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/162 X-Sequence-Number: 25482 Raf writes: > The final step was the decrement the reltriggers counter for the parent > table's pg_class entry to 0. This appears to have resolved the problem. You should probably have set it to 3 not 0; what you did has disabled *all* the triggers on that table. Is that really what you want? > I'm curious as to whether the problem may have resulted from slony > corruptting internal pg_ or postgres not correctly respecting the > integrity of drop-trigger type transactions and their respective > dependencies. You'd be better off asking about that on the Slony mailing lists. regards, tom lane