Re: BAKUP ISSUE - Mailing list pgsql-general

From hubert depesz lubaczewski
Subject Re: BAKUP ISSUE
Date
Msg-id CAKrjmhe9VhJfZ+juEBfpnv8m8vdsfx0Y1-pXDLfJ=a-M+PXmCg@mail.gmail.com
Whole thread Raw
In response to Re: BAKUP ISSUE  (hubert depesz lubaczewski <depesz@gmail.com>)
Responses Re: BAKUP ISSUE  (Michael Paquier <michael.paquier@gmail.com>)
Re: BAKUP ISSUE  (Marc Watson <mark.watson@jurisconcept.ca>)
List pgsql-general
On Wed, Jul 9, 2014 at 3:28 PM, Ramesh T <rameshparnanditech@gmail.com> wrote:
      Yes,not an error it is a warning  and archive is working.

How can you say that archive is working when in logs you have?
 
2014-07-09 18:53:33 IST LOG:  archive command failed with exit code 1
2014-07-09 18:53:33 IST DETAIL:  The failed archive command was: copy "pg_xlog\000000010000000000000001" "C:Program FilesPostgreSQL
amesh 000000010000000000000001"
2014-07-09 18:53:34 IST LOG:  archive command failed with exit code 1
2014-07-09 18:53:34 IST DETAIL:  The failed archive command was: copy "pg_xlog\000000010000000000000001" "C:Program FilesPostgreSQL
amesh 000000010000000000000001"
2014-07-09 18:53:34 IST WARNING:  archiving transaction log file "000000010000000000000001" failed too many times, will try again later

Fix the archive command so that it will actually work (files should appear in destination directory).

I have 0 knowledge about windows, but I would guess you need to use \\ and not \ in the path. Also - does the destination path exist?

depesz

pgsql-general by date:

Previous
From: dinesh kumar
Date:
Subject: Re: BAKUP ISSUE
Next
From: Scott Marlowe
Date:
Subject: Re: php password authentication failed for user ...