ohp@pyrenet.fr writes:
> I'm confused, until I have clearence to send the schema, here are pg logs:
> Nov 3 14:44:20 sun postgres[17963]: [189-1] ERROR: trigger "<unnamed>" for relation "objets" already exists
> Nov 3 14:44:20 sun postgres[17963]: [189-2] STATEMENT: CREATE CONSTRAINT TRIGGER "<unnamed>"
> Nov 3 14:44:20 sun postgres[17963]: [189-3] AFTER UPDATE ON objets
> Nov 3 14:44:20 sun postgres[17963]: [189-4] FROM objet_position
> Nov 3 14:44:20 sun postgres[17963]: [189-5] NOT DEFERRABLE INITIALLY IMMEDIATE
> Nov 3 14:44:20 sun postgres[17963]: [189-6] FOR EACH ROW
> Nov 3 14:44:20 sun postgres[17963]: [189-7] EXECUTE PROCEDURE "RI_FKey_noaction_upd"('<unnamed>',
'objet_position','objets', 'UNSPECIFIED', 'pobj_obj_cod',
> Nov 3 14:44:20 sun postgres[17963]: [189-8] 'obj_cod');
These must be hangovers from some truly ancient version of Postgres :-(
I'd suggest dropping all these triggers and setting up real foreign key
constraint declarations instead. If there seem to be too many to do it
manually, you might try contrib/adddepend which used to be included
with Postgres (between 7.3 and 8.1).
Looking into it, I think the reason you're getting bit now is that
CREATE CONSTRAINT TRIGGER didn't use to insist on a unique trigger name.
Now it does. But it's way past time for you to get rid of these
old-style foreign keys anyway.
regards, tom lane
