Thu Feb 3 16:28:00 PST 2005
- Previous message: [Slony1-general] redundent conninfo
- Next message: [Slony1-general] redundent conninfo
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On February 2, 2005 05:00 pm, Darcy Buskermolen wrote: > I've been busy working on an example that shows an overly complex and > advanced Slony-I replication cluster lay out (12 nodes). In the process of > setting it up I have found all sorts of ways to introduce head scratching > while trying to trouble shoot why events arn't propagating, most of it > related to conninfo. > > Is there a valid reason that we need to specify conninfo in more than one > place? I would think the only place we need it is in the "node N admin > conninfo" strings every where else can be implied by referenceing the node > id. Or am I missing something rather fundamental here? Nevermind, after looking at things a bit more indepth I have been wacked by the clue by four and realized that admin conninfo is distinct and only applies to slonik it has noting to do running of replication, only maintenance. Please disregard the noise. -- Darcy Buskermolen Wavefire Technologies Corp. ph: 250.717.0200 fx: 250.763.1759 http://www.wavefire.com
- Previous message: [Slony1-general] redundent conninfo
- Next message: [Slony1-general] redundent conninfo
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list