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

2005-03-27 Thread Devrim GUNDUZ
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On Sat, 26 Mar 2005, Devrim GUNDUZ wrote: Hmph. Those should be 'i' references to the foreign key constraint, not 'a' references to the relations. I suspect this database was carried forward from an ancient (pre-7.3) dump that defined the

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

2005-03-26 Thread Devrim GUNDUZ
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On Fri, 25 Mar 2005, Tom Lane wrote: Does \d pg_trigger show that the tgargs column is of type bytea? Umm no: tgnargs| smallint | not null tgargs, not tgnargs. Ooops, sorry. Ok, tgargs is of type bytea. Also, get the OID for this

[HACKERS] pg_dump issue : Cannot drop a non-existent(?) trigger

2005-03-25 Thread Devrim GUNDUZ
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I've Google'd for the situation below and could not find any solution. We are using PostgreSQL 8.0.1, installed using PGDG RPMs on RHEL ES 3.0: === prod=# SELECT version();

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

2005-03-25 Thread Stephan Szabo
On Fri, 25 Mar 2005, Devrim GUNDUZ wrote: - -- PostgreSQL 8.0.1 on i686-redhat-linux-gnu, compiled by GCC gcc (GCC) 3.2.3 20030502 (Red Hat Linux 3.2.3-42)

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

2005-03-25 Thread Tom Lane
Stephan Szabo [EMAIL PROTECTED] 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

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

2005-03-25 Thread Devrim GUNDUZ
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On Fri, 25 Mar 2005, Stephan Szabo wrote: === prod=# \d t_firma_moduller Table public.t_firma_moduller Column |

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

2005-03-25 Thread Devrim GUNDUZ
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Tom, On Fri, 25 Mar 2005, Tom Lane wrote: Stephan Szabo [EMAIL PROTECTED] 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

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

2005-03-25 Thread Tom Lane
Devrim GUNDUZ [EMAIL PROTECTED] 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

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

2005-03-25 Thread Devrim GUNDUZ
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On Fri, 25 Mar 2005, Tom Lane wrote: Devrim GUNDUZ [EMAIL PROTECTED] writes: prod=# select * from pg_trigger where tgname = 'RI_ConstraintTrigger_39053'; - -[ RECORD 1 ]--+--- tgrelid| 37564 tgname |

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

2005-03-25 Thread Tom Lane
Devrim GUNDUZ [EMAIL PROTECTED] writes: On Fri, 25 Mar 2005, Tom Lane wrote: Does \d pg_trigger show that the tgargs column is of type bytea? Umm no: tgnargs| smallint | not null tgargs, not tgnargs. Also, get the OID for this pg_trigger row and see if it shows up in objid or