Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 69C3E9FA4C1 for ; Wed, 3 Jan 2007 11:51:40 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-new, port 10024) with ESMTP id 37224-04 for ; Wed, 3 Jan 2007 11:51:26 -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 D86769FA4BC for ; Wed, 3 Jan 2007 11:51: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 1H28Oi-0001ok-Aw; Wed, 03 Jan 2007 15:51:24 +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 1H28O7-0001km-BM; Wed, 03 Jan 2007 15:50:47 +0000 From: "Sandy Spence" To: "'Tom Lane'" Cc: "'Rajesh Kumar Mallah'" , Subject: Re: Trigger trouble Date: Wed, 3 Jan 2007 15:51:04 -0000 Message-ID: <009301c72f4e$f9bfce40$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: <5247.1167838774@sss.pgh.pa.us> thread-index: AccvTaDL0mw/tLnSRZqWC0IPHxceQAAAJhKA X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 X-Sophos-Scanned: from axs@aber.ac.uk virus scanned OK X-UWA-Mid: 1H28O7-0001km-BM 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/11 X-Sequence-Number: 24167 Hi Tom, when I run the select query I get the following output, ltt=> select * from pg_type where typname='trigger'; typname | typowner | typlen | typprtlen | typbyval | typtype | typisdefined | typdelim | typrelid | typelem | typinput | typoutput | typreceive | typsend | typalign | typstorage | typdefault ---------+----------+--------+-----------+----------+---------+------------- -+----------+----------+---------+----------+---------- -+------------+---------+----------+------------+------------ trigger | 0 | 0 | 0 | f | | f | | 0 | 0 | - | - | - | - | i | p | trigger (1 row) I have a feeling that the database owner (ltt) has created their own type 'trigger' and am guessing that at some other time dropped an item (table maybe) that uses or used an instance of the type trigger. I have about 100 plus users databases on the same system and it only appears that this user is causing the pg_dump warning message. 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: Tom Lane [mailto:tgl@sss.pgh.pa.us] Sent: 03 January 2007 15:40 To: Sandy Spence Cc: 'Rajesh Kumar Mallah'; pgsql-admin@postgresql.org Subject: Re: [ADMIN] Trigger trouble "Sandy Spence" writes: > The version of postgres we are currently running is PostgreSQL 7.2.3 You sure it's not something newer? There wasn't any built-in type named "trigger" in 7.2 --- there is in 7.3 and up. Assuming it is 7.3, dropping the type would be a really bad idea. Could we see the results of "select * from pg_type where typname = 'trigger'"? I'm guessing that either that row is corrupt, or you dropped the original superuser account (in which case the gripe about type trigger is just the tip of the iceberg). regards, tom lane