On 07/22/2013 05:15 AM, Robert Wysocki wrote:
> Hi,
>
> After upgrading test environment to slony 2.1.2 from slony 2.0.7 I
> noticed, that previously flawless procedure done many times with EXECUTE
> SCRIPT like:
>
> CREATE TABLE ....;
> INSERT INTO audit VALUES ('new table');
>
> now fails with "duplicated primary key" error on slave nodes.
>
> How should this be done with slony>  2.1.2? I would like to avoid
> splitting it into DDL done with EXECUTE SCRIPT and DML done with psql.
>
> Regards,

It might help if you told us exactly what slonik EXECUTE SCRIPT command 
you were running and what your cluster looks like.

The slony log triggers should not fire if the set id in your execute 
script has an origin node equal to your event node.