On 03/15/2014 01:00 PM, Tory M Blue wrote:
>
>
>
> On Sat, Mar 15, 2014 at 9:36 AM, Steve Singer <ssinger at ca.afilias.info
> <mailto:ssinger at ca.afilias.info>> wrote:
>
>     On 03/15/2014 09:58 AM, Glyn Astill wrote:
>      >
>      >
>      >
>      > So Steve, can you advise on how to upgrade on systems with
>     multiple replication sets; Or am I just plain wrong that we can't
>     lock multiple sets at once?
>
>
>     I don't see any reason why you shouldn't be able to lock multiple
>     replication sets at the same time.
>
>
> Coming in late, is this a new procedure? I'm not sure I've ever locked
> tables with a slony upgrade in the past. I think I have simply stopped
> slony, upgraded, ran the slonik script and restarted.  Did I just get
> lucky or has something fundamentally changed?
>

This is special for upgrading from 2.0.x or 2.1.x to the 2.2.x series 
for the first time.  We changed the format of sl_log in the 2.2.x 
versions so you can't have any data still waiting to be replicated 
during the upgrade.



> thanks
> Tory
>
>
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at lists.slony.info
> http://lists.slony.info/mailman/listinfo/slony1-general
>