Fri Feb 18 16:42:57 PST 2005
- Previous message: [Slony1-general] replication stalled -- listen's can't be re-inserted
- Next message: [Slony1-general] replication stalled. listen's won't add
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Feb 18, 2005, at 11:34 AM, Christopher Browne wrote: > Note that the problem on node 2 is almost certainly NOT with events > stored on node 2; it is with events that node 2 is pulling from node > 3. You have to fix node 3's data for node 2 to come back online... > I rummaged around all the tables until such time that I figured this one out. Single delete on sl_event_1 on node3 and it caught up in about 5 minutes. I am totally amazed at the robustness of slony in the face of this kind of twiddling. Vivek Khera, Ph.D. +1-301-869-4449 x806
- Previous message: [Slony1-general] replication stalled -- listen's can't be re-inserted
- Next message: [Slony1-general] replication stalled. listen's won't add
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list