Re: Trigger trouble

On 12/22/06, Sandy Spence <axs(at)aber(dot)ac(dot)uk> wrote:
> Hi Rajesh,
>
> I ran the select query
> SELECT typowner from pg_type where typname='trigger';

In my installation \dT reports the type trigger
does it do so in yours? If it does not i am afraid
someone else shall be able to help you better.
regds
mallah.

psql>\dT *.trigger
List of data types
+------------+-----------+-------------+
| Schema | Name | Description |
+------------+-----------+-------------+
| pg_catalog | "trigger" | |
+------------+-----------+-------------+
(1 row)

Regds
mallah.

>
> 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(dot)rajesh(at)gmail(dot)com]
> Sent: 21 December 2006 20:04
> To: Sandy Spence
> Cc: pgsql-admin(at)postgresql(dot)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 <axs(at)aber(dot)ac(dot)uk> 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
> >
>
>