Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f28Hobx99343 for ; Thu, 8 Mar 2001 12:50:37 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id f28HoX928013; Thu, 8 Mar 2001 12:50:33 -0500 (EST) To: Frank Joerdens cc: pgsql-sql@postgresql.org Subject: Re: Re: How to drop an trigger In-reply-to: <20010308175126.A16939@rakete.joerdens.de> References: <20010308164246.A16533@rakete.joerdens.de> <20010308170629.A16771@rakete.joerdens.de> <20010308175126.A16939@rakete.joerdens.de> Comments: In-reply-to Frank Joerdens message dated "Thu, 08 Mar 2001 17:51:26 +0100" Date: Thu, 08 Mar 2001 12:50:33 -0500 Message-ID: <28010.984073833@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200103/181 X-Sequence-Number: 1834 Frank Joerdens writes: >> Just an idea: Is it safe to just delete the corresponding row in >> pg_trigger? > No, it ain't: After deleting the rows corresponding to the offending > triggers in pg_trigger, I can't vacuum, or dump. You need to adjust the reltriggers counts in the associated pg_class entries, too. regards, tom lane