Mon Nov 22 13:09:52 PST 2010
- Previous message: [Slony1-general] Features Summarized
- Next message: [Slony1-general] Feature Idea: improve performance when a large sl_log backlog exists
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi all, I am going to be upgrading slony cluster from 1.2.20 to 1.2.21 here soon, however before doing it I have some concerns. My cluster is a simple master to slave, however my slave daemon is writing out to archive files, which I am shipping to dozens of other nodes via log shipping. I've got the process down and tested it on some test boxes to upgrade and that works fine, however I'm wondering if the upgrade will cause the remote nodes to suddenly not be able to apply the archive logs being shipped to them. I am hoping that since this is a minor upgrade (20 -> 21), I would be surprised if this upgrade made any major modifications such as this, but I want to be sure. I don't think the remote nodes even have slony installed, they just have a dump of the slave database from when the nodes were set up from a modified version of the slon1_dump.sh file, which I believe is setting up the schema and environment they need (such as the _slony schema and functions). However I could be wrong on this. So long story short, upgrading from 1.2.20 to 1.2.21, will I need to push any updates to my remote boxes that are not part of the actual cluster, but just feeding off the archive logs created. Thanks in advance, - Brian F
- Previous message: [Slony1-general] Features Summarized
- Next message: [Slony1-general] Feature Idea: improve performance when a large sl_log backlog exists
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list