Re: pg_dump issue : Cannot drop a non-existent(?) trigger - Mailing list pgsql-hackers

Devrim GUNDUZ <devrim@gunduz.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