>Seems like a customer wants to change the PK of a replicated table...
>and
 from what i understood in the docs we shouldn't be using EXECUTE
>SCRIPT
 for that... i'm right?

Wrong! You do want to use EXECUTE SCRIPT. That insures the changed is propagated on all slaves at the same time. Just keep in mind that EXECUTE SCRIPT will lock all tables in a set. The big question is why is the primary key changing? If it's because the customer mistakenly wants to change the default sort order, or lookup, then it is best to just create another index on the tables.

Melvin Davidson 
From: Jaime Casanova <jcasanov at systemguards.com.ec>
Subject: [Slony1-general] [slony-general] changing the PK of a replicated table
To: "slony" <slony1-general at lists.slony.info>
Date: Monday, April 26, 2010, 11:26 AM

Hi,

Seems like a customer wants to change the PK of a replicated table...
and from what i understood in the docs we shouldn't be using EXECUTE
SCRIPT for that... i'm right?
so what are my options (besides to blame the customer for doing that)?
set drop table, change, readd it using a merge?

-- 
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157
_______________________________________________
Slony1-general mailing list
Slony1-general at lists.slony.info
http://lists.slony.info/mailman/listinfo/slony1-general



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20100426/dcd5e13b/attachment.htm