On Tue, 24 Feb 2009 09:31:17 -0500
Andrew Sullivan <ajs at crankycanuck.ca> wrote:

> On Tue, Feb 24, 2009 at 10:58:55AM +1300, Steve Holdoway wrote:
> 
> > I'm having a real problem getting this to work. What I'm trying to
> > do is to use a trigger on the replicated table to reformat the
> > information and add this to a dable in the same database, but a
> > separate schema. The trigger is firing, and the data is formatted
> > into an INSERT statement that is EXECUTEd. This fails with a
> > duplicate key ( on the remote table ) error.
> 
> Sounds like you have something wrong with your trigger function --
> maybe it's not doing what you think.  My bet is that your duplicate
> key is because something is firing more than once, but using the same
> values for something.
> 
> A
> 
> 
> -- 
> Andrew Sullivan
> ajs at crankycanuck.ca
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at lists.slony.info
> http://lists.slony.info/mailman/listinfo/slony1-general
Hi Andrew,

It works fine if I test it on an un replicated table, performing a bulk load either from a copy or multiple insert statements, which has sort of led me to dismiss that probability, and concentrate on environmental differences. If I remove the offending unique index, it fails on the next similar insert into a remote table, but there is still no data in the initial one...

I'm confused!

Steve 

-- 
Steve Holdoway <steve at greengecko.co.nz>