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

From: Devrim GUNDUZ <devrim(at)gunduz(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_dump issue : Cannot drop a non-existent(?) trigger
Date: 2005-03-25 18:18:56
Message-ID: Pine.LNX.4.61.0503251959020.26313@emo.org.tr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

On Fri, 25 Mar 2005, Tom Lane wrote:

> 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?

Umm no:

tgnargs | smallint | not null

> 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

Yes it is there

prod=# SELECT * from pg_depend WHERE objid =39053;
- -[ RECORD 1 ]------
classid | 16412
objid | 39053
objsubid | 0
refclassid | 1259
refobjid | 37564
refobjsubid | 0
deptype | a
- -[ RECORD 2 ]------
classid | 16412
objid | 39053
objsubid | 0
refclassid | 1259
refobjid | 37577
refobjsubid | 0
deptype | a

So... Is it with tgnargs issue? :(

Regards,

- --
Devrim GUNDUZ
devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr
http://www.tdmsoft.com http://www.gunduz.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFCRFYUtl86P3SPfQ4RAk1LAJ4wW13o7n29Fr52SY5/EbqNysh3PACgznyh
6RLdbTufPwP+vuHXc3+h1WE=
=AOBb
-----END PGP SIGNATURE-----

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Otto Blomqvist 2005-03-25 18:29:30 Re: pg_autovacuum not having enough suction ?
Previous Message Tom Lane 2005-03-25 18:04:48 pgsql: Fix two bugs in change_owner_recurse_to_sequences: it was