Skip site navigation (1) Skip section navigation (2)

Re: pg_dump issue : Cannot drop a non-existent(?) trigger

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Devrim GUNDUZ <devrim(at)gunduz(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_dump issue : Cannot drop a non-existent(?) trigger
Date: 2005-03-25 15:35:54
Message-ID: 23649.1111764954@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Devrim GUNDUZ <devrim(at)gunduz(dot)org> writes:
> prod=# select * from pg_trigger where tgname = 'RI_ConstraintTrigger_39053';
> - -[ RECORD 1 ]--+---------------------------
> tgrelid        | 37564
> tgname         | RI_ConstraintTrigger_39053
> tgfoid         | 1644
> tgtype         | 21
> tgenabled      | t
> tgisconstraint | t
> tgconstrname   | firma_moduller_firma_fkey1
> tgconstrrelid  | 37577
> tgdeferrable   | f
> tginitdeferred | f
> tgnargs        | 6
> tgattr         |
> tgargs         | firma_moduller_firma_fkey1

Well, that's consistent with what pg_dump said the tgargs value is;
but it ought to look like
firma_moduller_firma_fkey1\000t_firma_moduller\000t_firmalar\000UNSPECIFIED\000firma_no\000no\000
and the output from \d proves that that data is actually stored.  So why
isn't it being displayed??

Does "\d pg_trigger" show that the tgargs column is of type bytea?

Also, get the OID for this pg_trigger row and see if it shows up in
objid or refobjid of any rows of pg_depend.

It certainly seems that your system catalogs have been clobbered in
some odd way :-(

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2005-03-25 18:04:48
Subject: pgsql: Fix two bugs in change_owner_recurse_to_sequences: it was
Previous:From: Devrim GUNDUZDate: 2005-03-25 15:15:26
Subject: Re: pg_dump issue : Cannot drop a non-existent(?) trigger

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group