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

hannu at skype.net wrote:

|>>2) avoid it alltogether - could I load regular backup and start
|>>replication from there - somehow pg_dump seems to do fine ?
|>
|>No, you can't avoid it. And this is the part or your email that I don't
|>understand. How can pg_dump do fine?
|
| I think the fact that (dayly) pg_dump is ok, is due to it being run at the
| time of least activity. And that it manages to run fast enough run fully
| in that time.

That would be a good time to kick off subscribe set too.

|>It should even be worse because it
|>doesn't get slowed down by the subscriber building indexes on the fly.
|
| Could we somehow speed up our initial copy by dropping PK and other
| indexes during COPY and rebuilding them later ? I tried to do it manually
| after setting up replication but before subscribing but subscription also
| checked for existing pk.

You need the pk to run slony, but you can ditch all your other indices
and rebuild them later.

- --
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)

iD8DBQFBXZ8cgfzn5SevSpoRAkrUAJ0au5qK4YWypmenj50thnd/zEO4WgCgvVZ4
40duzzFU985OOkI16W2fUxE=
=usIA
-----END PGP SIGNATURE-----