<div align="left" ><div dir="auto" style="direction: ltr; margin: 0; padding: 0; font-family: sans-serif; font-size: 11pt; color: black; ">Hi<br>
<br>
</div>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0; font-family: sans-serif; font-size: 11pt; color: black; ">We are currently running our master server on SuSE 10 with Postgres 9.3 and Slony 2.2.3. Our slaves are running on CentOS, also with Postgres 9.3 and Slony 2.2.3.<br>
<br>
</div>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0; font-family: sans-serif; font-size: 11pt; color: black; ">We are running a project to upgrade the master to SuSE 12 and Postgres 9.6. Unfortunately Slony 2.2.3 would not install so we went up to 2.2.6. Unfortunately this means that we have to upgrade the slaves to 2.2.6 as well.<br>
<br>
</div>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0; font-family: sans-serif; font-size: 11pt; color: black; ">However, 2.2.7 has just been released which includes the enable_version_check feature.<br>
<br>
</div>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0; font-family: sans-serif; font-size: 11pt; color: black; ">If we went up to 2.2.7 on the master and turned version checking off, would this enable master and slaves to replicate, or would the version checking in the slave prevent it?<br>
<br>
</div>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0; font-family: sans-serif; font-size: 11pt; color: black; ">If turning off version checking does allow replication, are 2.2.3 and 2.2.7 compatible with each other?<br>
<br>
</div>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0; font-family: sans-serif; font-size: 11pt; color: black; ">Thanks<br>
<br>
</div>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0; font-family: sans-serif; font-size: 11pt; color: black; "> Andy<br>
<br>
</div>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0; font-family: sans-serif; font-size: 11pt; color: black; "><br>
</div>
</div>