Christopher Browne wrote:
It *is* necessary, upon this action, that configuration be reloaded, so
that the various nodes are aware of the change of node roles.
In version 1.2, this probably won't involve the slon actually falling over.
Consider it "not a huge problem" that it does, at this point, fall over.
Historically, one of the things we would traditionally try first, if we
ran into a replication problem, was to stop and restart the slons. It
would seldom cause significant problems, and often closing and reopening
database connections would resolve whatever was going wrong.
We don't do that quite so often; leaving slons up, and trying to figure
out what's up tends to be pretty useful in figuring out problem
conditions. But if you're not planning to spend time tracing things
unless you're forced to, "restarting the slons" is often pretty effective...
Christopher,
Thank you very much for the clarification.
_______________________________________________
Slony1-general mailing list
[email protected]
http://gborg.postgresql.org/mailman/listinfo/slony1-general
