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

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


Hi Tom,

On Fri, 25 Mar 2005, Tom Lane wrote:

> Stephan Szabo <sszabo@megazone.bigpanda.com> writes:
>> Odd, why is this not showing up as a foreign key constraint?  Has this
>> database been upgraded (no matter through how many different upgrades)
>> from an old version (7.1 or earlier I think)?
>
> And the other odd thing is that it fails to dump it as a trigger either.
> The "invalid argument string" complaint indicates that pg_dump didn't
> find the right number of "\000" sequences in the tgargs value; but
> pg_get_triggerdef evidently is finding the right number of zero bytes.
> It almost looks like the tgargs value got coerced from bytea to text
> somewhere between the catalogs and pg_dump, but how'd that happen?
>
> It'd be good to look at the trigger row directly:
>     select * from pg_trigger where tgname = 'RI_ConstraintTrigger_39053';

Here it is:

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


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)

iD8DBQFCRCsQtl86P3SPfQ4RAij+AJ4+p+Q9WrVTIo8xWR2YMWlgj9EoXgCgvhK8
n7CpjIeR54dcOyMg8hlb6w0=
=efYi
-----END PGP SIGNATURE-----