On 8/30/2007 9:37 AM, Brad Nicholson wrote:
> On Wed, 2007-08-29 at 20:23 -0400, Kurt Overberg wrote:
>> Brad,
>>
>> Thanks for the warning about log shipping on 1.1.5. I actually think
>> I ran across that bug soon after my post (my subscriber fell
>> waaaaaaay behind) :-)
>>
>> I'd like to upgrade, but this is a heavily used production cluster
>> that I somehow managed to cobble together and keep working (I'm
>> nowhere near a slony/pg expert, I'm just persistent), so I'm a little
>> nervous about upgrading slony across the entire thing (1 master, 3
>> subscriber nodes). The upgrade process seems deceptively simple
>> (compile new slony, get the libs into postgresql, then run update
>> functions), but is it really that simple? Should I not be nervous
>> and plow ahead? How easy is it to find a consultant who knows how to
>> do this stuff (confidently)?
>
> It is that simple, however you should be somewhat nervous and test it
> all out first. You'll likely want an outage during the upgrade. If
> not, you should at least force all connections to you database to be
> reset after the upgrade or you may hit some problems.
Changing from 1.1.5 to 1.2.11 is definitely a version jump where the
recommended procedure would be:
stop application(s)
stop slons
compile and install 1.2.11 on all nodes
run update functions on all nodes
start slons
start applications
Log shipping will get a nice boost very soon (around next week). I am
currently developing a tool that can be used to automatically pick up
the archive files, filter out tables or entire namespaces, rename tables
or namespaces on the fly and apply the result to a remote database or
ship it via scp and so on.
The tool will work with 1.2.11. Since it doesn't require any changes to
the existing code, it will be added to the 1.2 branch and subsequently
released in 1.2.12.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== [EMAIL PROTECTED] #
_______________________________________________
Slony1-general mailing list
[email protected]
http://gborg.postgresql.org/mailman/listinfo/slony1-general
