Glyn Astill glynastill at yahoo.co.uk
Tue May 17 08:25:06 PDT 2011
I presume this is the same as in 1.2.x, so after updating the binaries, run update_functions against each node.  Here's how I'd be doing it on our systems, where @Server<x> is the id of the node.


INCLUDE <preamble.inc.scr>;

UPDATE FUNCTIONS ( ID = @Server5a );
UPDATE FUNCTIONS ( ID = @Server5b );
UPDATE FUNCTIONS ( ID = @Server5c );
UPDATE FUNCTIONS ( ID = @Server5d );
UPDATE FUNCTIONS ( ID = @Server5e );




>________________________________
>From: raghu ram <raghuchennuru at gmail.com>
>To: slony1-general at lists.slony.info; slony1-general-request at lists.slony.info
>Sent: Tuesday, 17 May 2011, 14:48
>Subject: [Slony1-general] Upgrading Slony Minor version
>
>
>Dear all,
> 
>Currently we are running Slony-I 2.0.5 and we need to upgrade it to Slony-I 2.0.6.  
> 
>In the documentation there is UPDATE FUNCTION mentioned and not the steps. 
>http://www.slony.info/documentation/slonyupgrade.html
> 
>Can any one assist me steps how to upgrade the Slony-I 2.0.5 to Slony-I 2.0.6.
> 
>--Raghu Ram
>_______________________________________________
>Slony1-general mailing list
>Slony1-general at lists.slony.info
>http://lists.slony.info/mailman/listinfo/slony1-general
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20110517/0ebb9d2b/attachment.htm 


More information about the Slony1-general mailing list