-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 > Currently we use dump (to SQL file, i.e. pg_dump with no args) + file copy > to replicate the DB daily between the staging and web servers, and then > restore (via psql) the servers one at the time. In our application we expect > that average daily change is only to 3% of the records. My question is what > would be the best way to do this replication? Bucardo should handle this easy enough. Just install Bucardo, tell it about the databases, tell it which tables to replicate, and start it up. If the tables have unique indexes (e.g. PKs) you can use the 'pushdelta' type of sync, which will copy rows as they change from the staging server to the web servers. If the tables don't have unique indexes, you'll have to use the 'fullcopy' sync type, which, as you might imagine, copies the entire table each time. You can further control both of these to fire automatically when the data on the staging server changes, or to only fire when you tell it to, e.g. every X minutes, or based on some other criteria. You can also configure how many of the web servers get pushed to at one time, from 1 up to all of them. - -- Greg Sabino Mullane greg@xxxxxxxxxxxx End Point Corporation PGP Key: 0x14964AC8 200906121509 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iEYEAREDAAYFAkoyqFkACgkQvJuQZxSWSsjB8ACffcQRD+Vb7SV0RZnoo70hkpwB nycAn0QDiogs3EuCrc9+h4rMoToTFopz =Sltu -----END PGP SIGNATURE----- -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
