-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

You could use EXECUTE SCRIPT, but only if it's do-able on all of the
boxes at the same time (including the master). Otherwise you've gotta do
it by hand.

Also, if you're restarting replication on tables which are already
populated, you'll want to manually truncate them first.

Drew

Vivek Khera wrote:
| 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
|
|
| ------------------------------------------------------------------------
|
| _______________________________________________
| Slony1-general mailing list
| Slony1-general at gborg.postgresql.org
| http://gborg.postgresql.org/mailman/listinfo/slony1-general


- --
Andrew Hammond    416-673-4138    ahammond at ca.afilias.info
Database Administrator, Afilias Canada Corp.
CB83 2838 4B67 D40F D086 3568 81FC E7E5 27AF 4A9A
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFBYu0wgfzn5SevSpoRAmkQAKCH3WxZShXJdE5mzO3N6BJvvkyztACfedMv
u+DMwal0TnSi+uEye+CTZTY=
=5+Se
-----END PGP SIGNATURE-----