archive_command options? - Mailing list pgsql-admin

From LEROY TENNISON
Subject archive_command options?
Date
Msg-id 1222332414.512321.1554322572303@mail.yahoo.com
Whole thread Raw
Responses Re: archive_command options?  (Jerry Sievers <gsievers19@comcast.net>)
Re: archive_command options?  (Johannes Truschnigg <johannes@truschnigg.info>)
Re: archive_command options?  (Keith Fiske <keith.fiske@crunchydata.com>)
Re: archive_command options?  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-admin
Postgresql documentation lists the following as an archive command for log shipping:

archive_command = 'test ! -f /mnt/server/archivedir/%f && cp %p /mnt/server/archivedir/%f'

The problem is that it is very fragile.  If anything breaks the copy (either system failing, network issues) then log shipping stops because the file exists in some intermediate state.  The result is that logs build up on the source system filling disk space.  I've had to deal with a few of these this week, in two cases the file system was 98% full.  Is there a reason rsync isn't used?  It has the ability to restart interrupted transfers.  I don't want to use it only to find out i got myself into another predicament.  Any other less-fragile options?  Thanks for the help.

pgsql-admin by date:

Previous
From: soumitra bhandary
Date:
Subject: Re: Configuration of django with master slave replication Postgres
Next
From: Jerry Sievers
Date:
Subject: Re: archive_command options?