Running Slony 1.2.2 against postgres 8.1.3 (master and one slave),  
new slave postgres 8.2.0;

I just tried to move my second slave node to postgres 8.2.0. I'm  
replicating a database that's about 37 GB in size.

Initial replication is lagging. A table that's about 5 GB in size is  
still replicating after 7 hours (!) on a local network. I see nothing  
in the slony logs indicating any problems, but progress is glacially  
sloooow.

In the logs for the postgresql 8.2 server, I do see that suggestions  
that I need to increase the checkpoint_segments size. I have this  
tweaked quite high on the 8.1.3 servers; and screwed up and left the  
default value on the new 8.2.0 server.

I'm tempted to do a DROP NODE on the lagging slave and increase the  
checkpoint segments size -- but two questions:

1) Is there a way to drop the node if it's way behind in the slony  
logs? If I have to wait until it catches up to drop it, I could be  
waiting for hours.

2) Is there any other suggestions I might use to speed up initial  
replication? I've already tried restarting the slony process once;  
that wasn't fun -- it rolled back the replication of the slave node  
to the start, and so I had to wait 5 hours to get back to the same  
sticky point.

Thanks in advance...


######################################################################
This e-mail is confidential and should not be redistributed or
forwarded by the recipient except with the permission of the sender.  
The information contained in this e-mail message is intended only for 
the use of the individual or entity named above.  If the reader of 
this message is not the intended recipient or you have received 
this communication in error, please immediately notify us by 
telephone.  Receipt by anyone other than the intended recipient is 
not a waiver of any work-product or, if applicable, attorney-client 
privilege.

This e-mail does not constitute an offering of any security.  Such an
offering may only be made by means of a private placement memorandum
or other disclosure document.  Nothing in this e-mail constitutes
investment advice.  Past performance is not indicative of future
results.  All e-mail to and from Millburn Ridgefield Corporation and
its affiliates is monitored, stored and made available to regulators
if requested.
######################################################################