Tue Feb 14 00:14:32 PST 2006
- Previous message: [Slony1-general] cleanupNodeLock
- Next message: [Slony1-general] replicating set doesnt seem to be replicating
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
3 node setup. I moved the origin of a set from svr1 to sv3, and now svr2 doesn't appear to be updating anymore, even after issuing a subscribe set to specifically point svr2 to svr3. sl_status on all three nodes shows no signifigant lag_time, sl_subscribe shows svr2 as a reciever for svr3 and svr1 with both active. even sl_event seems to have timestamps relativly inline on all three machines. the thing is that the count(*) on the tables and the values of the sequences are not updating on the svr2 machine, as if there was no updating going on. is there something else i should be looking for? suppose i could create the setup on svr2 but theres a large table involved that i'd rather not have to resync... anyone have pointers on jump starting svr2 again? -- Robert Treat Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
- Previous message: [Slony1-general] cleanupNodeLock
- Next message: [Slony1-general] replicating set doesnt seem to be replicating
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list