On 01/06/2014 03:18 AM, Martijn van Oosterhout wrote:
Hoi,
I've setup a up WAL shipping configuration as described in the wiki. On
the master I have:
archive_mode = on
archive_command = 'cp %p /path_to/archive/%f'
and on the slave in the recovery.conf I have:
archive_cleanup_command = 'pg_archivecleanup /path/to/archive/ %r'
restore_command = 'cp /path/to/archive/%f %p'
In between the two machines I have an rsync process copying the files
from the master to the slave.
My problem is, that the archive_cleanup_command on the slave is
clearing old WAL files, which the rsync on the master just copies again
because they are still on the master.
I can make a script on the master that deletes files older than an
hour, but that will break horribly if the copying breaks for an hour.
Is there a smarter way to do this, like having rsync not copy stuff
already copied once?
So the rsync and archive_command combination is a belt and suspenders thing?
As to rsync, if I understand what you want you might take a look at
--existing:
http://linux.die.net/man/1/rsync
--existing, --ignore-non-existing
This tells rsync to skip creating files (including directories)
that do not exist yet on the destination. If this option is combined
with the --ignore-existing option, no files will be updated (which can
be useful if all you want to do is delete extraneous files).
Thanks in advance,
--
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
