Well, I'm kind of leaning towards having the functionality to remove 
indexes during the copy, then add them afterwards, but before the 
replication continues.

Why?

Well, in my testbed, I'm *still* doing the initial copy since about 
midnight friday of one of my large tables.  Granted, the machine isn't 
that fast, but restoring the same DB on it takes only a few hours.

If I could specify to slon an SQL script to run on the slaves after the 
initial copy that would recreate the indexes/unique constraints, then 
I'm sure it would take less time to copy this table.


Vivek Khera, Ph.D.
+1-301-869-4449 x806
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2476 bytes
Desc: not available
Url : http://gborg.postgresql.org/pipermail/slony1-general/attachments/20041004/86363198/smime.bin