On 04/22/2013 12:16 PM, Moshe Jacobson wrote:
On Mon, Apr 22, 2013 at 1:41 PM, Christophe Pettus <xof@xxxxxxxxxxxx
<mailto:xof@xxxxxxxxxxxx>> wrote:
> Not bad, but the transaction logs would fill up the file system.
I'm not sure I understand that comment. Why would the transaction
logs be particularly voluminous in this case?
I assumed the logs would be shipping to the slave and accumulating if
the replication stopped. Is that not the case?
Is it possible for the slave to pause replication indefinitely and pick
up where it left off without requiring huge volumes of transaction logs?
Besides, it would not be worth it to set up a whole database cluster just for this purpose.
It does seem to meet all of your needs in a very efficient way;
setting up a PG cluster is not that complex.
We don't have enough disk space to create a whole new copy of the
database cluster. Until now we have been restoring from a pg_dump backup
that does not include all of the audit logs.
Tools that allow more selectivity, in no particular order:
Bucardo http://bucardo.org/wiki/Bucardo
Slony http://slony.info/
Londiste http://skytools.projects.pgfoundry.org/doc/londiste.ref.html
Thanks!
--
Moshe Jacobson
Nead Werx, Inc. | Manager of Systems Engineering
2323 Cumberland Parkway, Suite 201 | Atlanta, GA 30339
moshe@xxxxxxxxxxxx <mailto:moshe@xxxxxxxxxxxx> | www.neadwerx.com
<http://www.neadwerx.com/>
"Quality is not an act, it is a habit." -- Aristotle
--
Adrian Klaver
adrian.klaver@xxxxxxxxx
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
