<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div>Hi</div><div><br></div><div>I use Slony 1.2.22</div><div><br></div><div>Replication: 1 master and 3 slaves.</div><div><br></div><div>We are used to update our Production Database every 2 or 3 months.</div><div><br></div><div>Updating Production Database <br></div><div><br></div><div>- is done on a week-end. There is no connexion from client (rejected) only master and all slaves<br></div><div>can connect each other.</div><div><br></div><div>- implies to use DDL query on tables (alter table add ....and so on).</div><div><br></div><div>For the moment and for each update, we are used to build replication from scratch.</div><div>I know it is not a good way.<br></div><div><br></div><div>"Slony command DDL" can not be used because it will take to much time and we've got a lot of replicated tables.</div><div>I am afraid that
window of week-end will be not enough.<br></div><div><br></div><div>For the next update, what I would like to suggest to my team ( and we will have the intention to test if I can convice them) is <br></div><div><br></div><div>1) removing all tables - to be altered - from replication using set drop table(origin=??,id=??)</div><div><br></div><div>2) apply all DDL queries to the future altered table ( usual way : psql ....database)<br></div><div><br></div><div>3) back all altered tables to replication :</div><div> - create set (...)</div><div> - set add table(...) to new set</div><div> - merge set (new set to the old set associated to the altered table).</div><div><br></div><div>Can we do that? </div><div><br></div><div>There is no concurrent activity and we've got the window of the
week-end.</div><div><br></div><div>Thanks for your reply.<br></div></div></body></html>