Hi All,
Using Slony1 version 1.1.0 at a customer site, the customer has had the
slon daemons fall over on one of their slave servers (and didn't
notice!) On restarting the slon processes, there is now an error being
generated because it is attempting to malloc memory to record all of the
outstanding transactions and the slon daemon is running out of memory.
Is there any way forward to resolve this, or will I just have to
uninstall the slave and resubscribe (which is my current plan).
Thanks
Peter Davie
--
Relevance... because results count
Relevance Phone: +61 (0)2 6241 6400
A.B.N. 86 063 403 690 Fax: +61 (0)2 6241 6422
Unit 11, Mobile: +61 (0)417 265 175
Cnr Brookes & Heffernan Sts, E-mail: [EMAIL PROTECTED]
Mitchell ACT 2911 Web: http://www.relevance.com.au
_______________________________________________
Slony1-general mailing list
[email protected]
http://gborg.postgresql.org/mailman/listinfo/slony1-general
