"Chung Wu" <[EMAIL PROTECTED]> writes: > Yup, restarting the slony processes did help. Odd, that. Thanks!
In the *distant* past, "restart the slons" was a near-universal first answer to all problems we had. I'd restart the slons, on the possibility that *something* had gotten wedged up. It was generally easy to do, entirely safe, and often resolved these sorts of things. Things have stabilized enough over the last couple of years that we tend more to gnaw on the problems a bit to see if there's some sort of lock or something outstanding that is the *true* problem. Nonetheless, restarting slons is quite safe (unless an 18-hour-long subscription is in progress), and unless you're keen on digging, that's a good thing to try early on, *particularly* if there's anything about your network that might be unreliable. For instance, if you've got a WAN / VPN tunnel that traffic goes over, it's possible for connections to fall over and possibly even 'recover' without announcing this. Your existing DB connection may be dead, but it doesn't know it. Restarting the slon may clear this sort of thing out... -- (reverse (concatenate 'string "ofni.sailifa.ac" "@" "enworbbc")) <http://dba2.int.libertyrms.com/> Christopher Browne (416) 673-4124 (land) _______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
