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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 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" <[EMAIL PROTECTED]> 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 ---------------------------(end of broadcast)--------------------------- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate