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

Hi,

One of the table I have in a set of replication (123 tables or such) contains
some 6 000 000 rows. Let's call it mybigtable (MBT).

I need to update more than 300 000 rows at once in MBT.

I wonder what the best option is.

Indeed, I see three options :

 1. update MBT on master, and wait ;
 2. drop MBT out of replication, update it, and then add it back to the
replication;
 3. move MBT to a new set, update rows, and then merge sets back.

One of the slaves (1 master, 9 slaves) is really far from master, and link is
quite slow.

Thus, I'm afraid first solution could lead to wait for too many hours.

When first initialising the replication, I had to wait for some 2 hours and
half for the farest node to be in sync. I think it could be far longer to wait
for that many rows updated on that slave.

That's why I thought of solution 2. BTW, updating 320 000 rows on master could
take some 20 minutes or so.

What's more I wonder if slony could work two sets in parallel so that I don't
have to wait for MBT to be updated and other tables can stay in touch with
master while processing MBT updates.

Any advice is welcome.

Best regards,
- --
Stéphane Schildknecht
PostgreSQLFr - http://www.postgresql.fr
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFKMP1wA+REPKWGI0ERAijCAJ93yAIgBbwYBx5j4/uXtIUsXmn73ACZASt8
xgvvErD5dviNBxsCThPaE2g=
=ruFz
-----END PGP SIGNATURE-----