Thu Sep 8 22:25:13 PDT 2005
- Previous message: [Slony1-general] Forcing an existing node to copy data fresh
- Next message: [Slony1-general] Forcing an existing node to copy data fresh
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jim Archer wrote: >Tim Goodaire said: > > > >>Often, if you're sending events through and they're not showing up on >>all of the nodes, it's one of the following: >> >>1. A slon isn't running >>2. Your paths are wrong >>3. Your listen network is wrong >>4. You haven't waited long enough for the event to propogate through to >>all of the nodes >> >> > >Hm, on Slony 1.1, do I have to manually specify the listen network? I >thought that was handled automagically from the path statements. If not, >that could be my problem... > > > It is handled automatically in 1.1. It's still worth having a look to see if it's setup properly, though. -- Brad Nicholson 416-673-4106 Database Administrator, Afilias Canada Corp.
- Previous message: [Slony1-general] Forcing an existing node to copy data fresh
- Next message: [Slony1-general] Forcing an existing node to copy data fresh
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list