From: | Dimitri Fontaine <dfontaine(at)hi-media(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, ohp(at)pyrenet(dot)fr, Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
Subject: | Re: should I worry? |
Date: | 2007-11-02 20:22:57 |
Message-ID: | 200711022122.57556.dfontaine@hi-media.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
Le Friday 02 November 2007 21:08:24 Tom Lane, vous avez écrit :
> No, foreign-key triggers always have names too, and they don't look like
> that (they look like RI_ConstraintTrigger_nnn). I cannot find anyplace
> in PG that supplies "<unnamed>" as a default name for a trigger, either.
> So there's something weird about your schema, and we really need to
> see a test case ...
I've had some restore problems with "<unnamed>" triggers on a 8.1 database. It
contained some de-activated triggers dating from pre-7.3 era, and I finally
managed to clean out the schema with the adddepend contrib utility.
http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/adddepend/Attic/
After running this, I had no more problems related to unnamed triggers, but I
can't remember the specifics of the errors I had. For adddepend to run, some
data were to be removed, too (disabled constraint triggers made possible to
insert them at some point in the past).
Sorry for the imprecision of the post, hope this helps,
--
dim
From | Date | Subject | |
---|---|---|---|
Next Message | Gevik Babakhani | 2007-11-02 20:43:04 | Continue [PATCHES] V0.1 patch for TODO Item: SQL-language reference parameters by name. |
Previous Message | Tom Lane | 2007-11-02 20:08:24 | Re: should I worry? |