<br>Hi all,<br>I'm evaluating for my current project. <br><br>I suspect this question has been answered several times but I checked the docs and google and I didn't found a clear answer.<br><br>Can slony be used if the slave schemas are slightly different from the master one?<br>
<br>We have a 1 master and 2 slave installations of a system automation application. The application can be upgraded independently on the three nodes.<br><br>So this could be an actual scenario:<br><br>master: version 1.34<br>
slave1: version 1.35<br>slave2: version 1.32<br>
<br>Any version update could imply some schema changes, for example:<br><br>- add/drop/modify a column<br>- add/drop a table<br><br>The schema changes must NOT be replicated because any version of the running application expects different schemas (of course small changes can be replicated without problems).<br>
<br>What I'd like slony to do is to handle missing columns (with defaults if not null), extra columns (ignoring), and for big changes transform data through a custom script.<br><br>Can this be achieved? <br><br>It's acceptable, for the most complex cases, to use temporary tables to save changes to be applied later on the actual ones.<br>
<br><br>Thanks for any pointer<br><br><br>Bye<br><br>Lorenzo<br><br><br>