Hi – we are running postgres 8.3.11 and two weeks ago started slony 2.0.5 on
a VM slave, and a standalone
Master.  The database approaches 200 GB in size and the subscription process
took about 16 hours
Success!  Unforturately the NEXT day the underlying server on the vm slave
experienced a 
Hardware memory crash and we lost connectivity. 

We now have the hardware crash resolved and wish 
to restart slony this weekend. 
I have verified that there have been no schema changes.
 Should I:
  1. issue a ./slon_start and allow slony to catch-up two weeks worth of 
     updates
        Or
  2. Punt, start from scratch, redefine everything and rerun the 16 hour
     subscription process?

Master config:

Linux ar-db-psql-1desq 2.6.18-194.11.3.el5 #1 SMP Mon Aug 30 16:19:16 EDT
2010 x86_64 x86_64 x86_64 GNU/Linux

Slave config:

Linux ar-db3-phys 2.6.18-194.26.1.el5 #1 SMP Tue Nov 9 12:54:20 EST 2010
x86_64 x86_64 x86_64 GNU/Linux

Thank you,

   
Mark Steben | Database Administrator 
@utoRevenue® - "Keeping Customers Close" 
95D Ashley Ave, West Springfield, MA 01089 
413.243.4800 x1512 (Phone) |413.732-1824 (Fax) 
@utoRevenue is a registered trademark and a division of Dominion
Enterprises