Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id C22329FA4CA for ; Wed, 3 Jan 2007 11:20:38 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-new, port 10024) with ESMTP id 71574-01 for ; Wed, 3 Jan 2007 11:20:27 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from tweli.aber.ac.uk (tweli.aber.ac.uk [144.124.16.41]) by postgresql.org (Postfix) with ESMTP id 6A7899FA4BC for ; Wed, 3 Jan 2007 11:20:26 -0400 (AST) Received: from localhost ([127.0.0.1] helo=tweli.aber.ac.uk) by tweli.aber.ac.uk with esmtp (Exim 4.54) id 1H27uh-0007WD-Bt; Wed, 03 Jan 2007 15:20:23 +0000 Received: from pc2axs.dcs.aber.ac.uk ([193.60.11.82] helo=pc2axs) by tweli.aber.ac.uk with esmtp (Exim 4.54) id 1H27uU-0007VX-Bw; Wed, 03 Jan 2007 15:20:11 +0000 From: "Sandy Spence" To: "'Tom Lane'" Cc: "'Rajesh Kumar Mallah'" , Subject: Re: Trigger trouble Date: Wed, 3 Jan 2007 15:20:23 -0000 Message-ID: <008d01c72f4a$b3103e20$520b3cc1@pc2axs> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <23990.1166798369@sss.pgh.pa.us> thread-index: Accl11lQQCx/GOAJSOSuIGMJRynqrQJcmmYA X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 X-Sophos-Scanned: from axs@aber.ac.uk virus scanned OK X-UWA-Mid: 1H27uU-0007VX-Bw X-UWA-Originating-IP: 193.60.11.82 X-UWA-Bounce-Filter: XYm0cVKk X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200701/9 X-Sequence-Number: 24165 Hi Tom, Thanks for the reply, sorry for the delay in responding a Scotsman and Hogmanay are never parted ;~} The version of postgres we are currently running is PostgreSQL 7.2.3 I did a Drop type trigger on the users database adding a tab at the end and came up with the list below RI_ConstraintTrigger_6081987 RI_ConstraintTrigger_6081995 RI_ConstraintTrigger_6082037 bestworkbehave RI_ConstraintTrigger_6081989 RI_ConstraintTrigger_6081997 RI_ConstraintTrigger_6121610 pg_sync_pg_pwd RI_ConstraintTrigger_6081991 RI_ConstraintTrigger_6082033 RI_ConstraintTrigger_6121612 tidyup RI_ConstraintTrigger_6081993 RI_ConstraintTrigger_6082035 RI_ConstraintTrigger_6121614 as you can see there appears to be an instance of a trigger that is not connected to anything, is there a table that has an entry where I can remove the offending trigger? Cheers, Sandy Computer Officer, RA Certification Manager Department of Computer Science - UWA Llandinam Building Penglais Campus Aberystwyth Ceredigion Wales - UK SY23 3DB Tel: (01970)-622433 Fax: (01970)-628536 -----Original Message----- From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Tom Lane Sent: 22 December 2006 14:39 To: Sandy Spence Cc: 'Rajesh Kumar Mallah'; pgsql-admin@postgresql.org Subject: Re: [ADMIN] Trigger trouble "Sandy Spence" writes: > select typowner from pg_type where typname='trigger'; typowner > ---------- > (0 rows) Um ... what PG version is this exactly? ("select version()" if you're not sure.) It's real hard to see why pg_dump would complain about a type that's not there at all. You sure you checked this in the same database that's being dumped? regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq