On 12/7/2005 9:23 PM, Peter Davie wrote:
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).
This node must have been down for quite some time. A SYNC event in the
remote_worker queue takes about 200 bytes or so. How many million events
is this node behind? You could tell from looking at sl_status.
And don't forget to VACUUM FULL ANALYZE that database after you've
dropped that node.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== [EMAIL PROTECTED] #
_______________________________________________
Slony1-general mailing list
[email protected]
http://gborg.postgresql.org/mailman/listinfo/slony1-general
