From: Greg Sabino Mullane <greg@turnstep.com>
To: pgsql-admin@postgresql.org
Subject: Re: replication recommendation
Date: Mon, 19 Jul 2010 21:38:50 -0000
Message-ID: <d4dc1ab1ba6aac77a7dd202aa3d47e1b@biglumber.com> (raw)
In-Reply-To: <1ED27F53E51B944F8498BDD54B54E3DB038B63493E@FALCON.omni.imsweb.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
> We are running PG 8.4.4 on Suse 9 and would like to set up a
> master/slave configuration but have the following requirements:
> - we want to be able to freeze the slave and only force it to update 'on demand'
> - we have data in other schemas in the slave database that we would like to preserve
>
> The master and slave will exist on different servers if that helps.
> The master DB is roughly 40 GB in size. I realize we could do a dump on
> master and restore to slave, but it seems like there might be a more elegant
> and efficient solution.
This could be accomplished with Bucardo (http://bucardo.org). Setup a sync,
make sure "ping" is off (so it does not automatically update the slave
on master activity), and then you can manually "kick" the sync whenever you
want to update the slave. (Apologies for all the Bucardo terminology)
Some possible drawbacks:
* Bucardo can only replicate tables incrementally that have a primary
key or a unique index. If the table has neither, it can only copy
the entire table each time.
* If you go a long time between slave updates, the table that holds
queued changes on the master will get quite large, and the update
will, naturally, take longer. Both are not too much of a concern, but
if you have tables that change nearly all of their data between updates,
you may want to switch to a different method and copy the entire table
instead.
- --
Greg Sabino Mullane greg@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201007191737
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----
iEYEAREDAAYFAkxExdYACgkQvJuQZxSWSshTMgCgmNBMil740wtFMtAut083GKET
dv8AoOqhtNLy5orQGOJK4eZrWJzbJxG9
=iUBd
-----END PGP SIGNATURE-----
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: greg@turnstep.com
Subject: Re: replication recommendation
In-Reply-To: <d4dc1ab1ba6aac77a7dd202aa3d47e1b@biglumber.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox