Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 6E7F99FA394 for ; Fri, 22 Dec 2006 05:44:56 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024) with ESMTP id 21117-03 for ; Fri, 22 Dec 2006 05:44:31 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from braint.aber.ac.uk (braint.aber.ac.uk [144.124.16.42]) by postgresql.org (Postfix) with ESMTP id 8EAB79F93A2 for ; Fri, 22 Dec 2006 05:44:31 -0400 (AST) Received: from localhost ([127.0.0.1] helo=braint.aber.ac.uk) by braint.aber.ac.uk with esmtp (Exim 4.54) id 1Gxgx3-0004gR-3b; Fri, 22 Dec 2006 09:44:29 +0000 Received: from pc2axs.dcs.aber.ac.uk ([193.60.11.82] helo=pc2axs) by braint.aber.ac.uk with esmtp (Exim 4.54) id 1GxgwJ-0004cq-3H; Fri, 22 Dec 2006 09:43:43 +0000 From: "Sandy Spence" To: "'Rajesh Kumar Mallah'" Cc: Subject: Re: Trigger trouble Date: Fri, 22 Dec 2006 09:44:05 -0000 Message-ID: <000801c725ad$b8299010$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: thread-index: AcclO3iZ7jpfswnUQlCHF0ul45natwAcWWQg X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 X-Sophos-Scanned: from axs@aber.ac.uk virus scanned OK X-UWA-Mid: 1GxgwJ-0004cq-3H X-UWA-Originating-IP: 193.60.11.82 X-UWA-Bounce-Filter: bUtrEqC66dw X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200612/294 X-Sequence-Number: 24086 Hi Rajesh, I ran the select query SELECT typowner from pg_type where typname='trigger'; with the following results select typowner from pg_type where typname='trigger'; typowner ---------- (0 rows) I then ran the second select query SELECT * from pg_user; (I also changed slightly select usename, usesysid from pg_user where usename='ltt';) usename | usesysid ---------+---------- ltt | 3517 (1 row) user/database is where the warning message for the trigger originates from. Is there something significant in the first select statement. Regards, 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: Rajesh Kumar Mallah [mailto:mallah.rajesh@gmail.com] Sent: 21 December 2006 20:04 To: Sandy Spence Cc: pgsql-admin@postgresql.org Subject: Re: [ADMIN] Trigger trouble Sandy, SELECT typowner from pg_type where typname='trigger'; check if typeowner exists in the column usesysid of pg_user by doing SELECT * from pg_user ; if typeowner does not exists there is a problem. regds On 12/21/06, Sandy Spence wrote: > Hi All, > > I get the following error when performing a pg_dump > > dumping database "ltt"... > pg_dump: WARNING: owner of data type trigger appears to be invalid > > the owner and database exists, I have run the following select > statement, > > select pg_class.oid, pg_trigger.tgrelid from pg_trigger left join > pg_class on pg_trigger.tgrelid=pg_class.oid; > > oid | tgrelid > ---------+--------- > 1260 | 1260 > 6081779 | 6081779 > 6081981 | 6081981 > 6081779 | 6081779 > 6081779 | 6081779 > 6081981 | 6081981 > 6081975 | 6081975 > 6081975 | 6081975 > 6082027 | 6082027 > 6081779 | 6081779 > 6081779 | 6081779 > 6082027 | 6082027 > 6121607 | 6121607 > 6121268 | 6121268 > 6121268 | 6121268 > > so it appears that it is not a dropped table causing the warning, is > there any other way I can try to determine how this warning is being > produced, is there a way of viewing the contents of the trigger? > > Thanks in advance, > > 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 > > > > ---------------------------(end of > broadcast)--------------------------- > TIP 7: You can help support the PostgreSQL project by donating at > > http://www.postgresql.org/about/donate >