----- Original Message -----
> From: Steve Singer <[email protected]>
> To: Vick Khera <[email protected]>
> Cc: slony <[email protected]>
> Sent: Friday, 14 March 2014, 17:30
> Subject: Re: [Slony1-general] question about upgrading 2.1 to 2.2 steps from
> manual
>
> On 03/13/2014 02:43 PM, Vick Khera wrote:
>> In the docs, a suggested method to upgrade 2.1 to to 2.2 is as follows:
>>
>> 1. Use SLONIK LOCK SET to lock all sets, so that no new changes are
>> being injected into the log tables
>> 2. Set slon parameter slon_config_cleanup_interval to a very low value
>> (a few seconds) so that the slon cleanup thread will trim data out
>> of sl_log_1 and sl_log_2 immediately
>> 3. Restart slon for each node and let it run through a cleanup cycle to
>> empty out sl_log_1 and sl_log_2 on all nodes.
>> 4. Verify that sl_log_1 and sl_log_2 are empty on all nodes in the
> cluster.
>> 5. Use SLONIK UPDATE FUNCTIONS against each node to upgrade to version 2.2
>> 6. Use SLONIK UNLOCK SET to unlock all sets
>>
>> Based on my experience and other reading, I think between steps 4 and 5
>> should be:
>>
>> 1. stop slon
>> 2. install new version of slony
>>
>> then after step 5, restart slon.
>>
>> Is that the correct place to perform the install? Or can/should that be
>> done between steps 2 and 3?
>
> You want to run step 3 with the OLD slon, thew new slon won't work yet.
>
> So yes, between steps 4 and 5 is when you would install the new slon
>
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?
_______________________________________________
Slony1-general mailing list
[email protected]
http://lists.slony.info/mailman/listinfo/slony1-general
