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

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

From: Devrim GUNDUZ <devrim(at)gunduz(dot)org>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_dump issue : Cannot drop a non-existent(?) trigger
Date: 2005-03-27 19:31:18
Message-ID: Pine.LNX.4.61.0503272224150.11072@emo.org.tr (view raw or flat)
Thread:
Lists: pgsql-hackers
-----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 triggers
>> by "CREATE CONSTRAINT TRIGGER" instead of "ALTER ADD FOREIGN KEY".
>
> I haven't coded the application but AFAIKit was developed using 7.4 and
> 7.5(CVS); and we installed database on 8.0.1... This is a new app.

Ok, sorry for the wrong info. I learned that they had begun coding the app 
on 7.2, then moved to 7.3->7.4->8.0... You are right.

>> Have you ever run contrib/adddepend to update the definitions to be
>> proper constraints?

Ok, running adddepend solved our problem (in fact it produced some erros 
related to perl but we ran the queries inside psql and fixed the problem). 
Now we can run pg_dump.

Thanks all.

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)

iD8DBQFCRwoItl86P3SPfQ4RApMRAKCv7EZ1yd9UwBMLbLTBgju3pqcBzACfSYqI
z2m1MsjhQWzeezM3WNKADgQ=
=c3Fv
-----END PGP SIGNATURE-----

In response to

pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2005-03-27 19:39:17
Subject: _RollbackFunc : dead code?
Previous:From: Magnus HaganderDate: 2005-03-27 18:11:48
Subject: Re: Patch for collation using ICU

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