On Wed, Nov 24, 2010 at 12:52 PM, DM dm.a...@gmail.com wrote:
Here is my Archive Command:
archive_command = 'cp -i %p /mnt/nfs/primary/%f /dev/null'
Just curious... why would you turn on the interactive version of cp
for an automated script? Is that why you feed it /dev/null as input?
--
I thought that when I first read about WAL archiving but the documentation
explains quite well. Basically it is to stop a successful result being
returned in the event that the file already exists in the archive
destination (to cause an error in the event it tries to overwrite a file).
On Thu,
Hi All,
pg_stop_backup is not stopping...
Postgresql version 9.01
OS: Centos
Postgresql.conf == default configuration did not change anything
Steps
1. Initiated psql -c SELECT pg_start_backup('label', true)
2. Started RSYNC job to sync slave box
rsync -a /var/lib/pgsql/data/
Deepak,
Does your backup script exclude the pg_xlog directory? There is no point
backing up the WAL files but you will want to make sure the archived WAL
files are added to the backup set afterwards.
How many files are in pg_xlog at the point where you stop the backup? It
may actually be that
Hi Mathew,
Thanks for your reply.
Its a test machine, I am testing streaming replication with archive.
I figured out he problem, the /mnt/nfs didnt had enough space.
Thanks for looking into this issue.
Thanks
Deepak
On Wed, Nov 24, 2010 at 10:36 AM, Matthew Walden
