Re: BAKUP ISSUE
| От | Marc Watson |
|---|---|
| Тема | Re: BAKUP ISSUE |
| Дата | |
| Msg-id | 02F1BBB48ABD3245A3BC519B57CFC8CA5DB41452@Exchange.JurisConcept.local обсуждение исходный текст |
| Ответ на | Re: BAKUP ISSUE (hubert depesz lubaczewski <depesz@gmail.com>) |
| Список | pgsql-general |
De : pgsql-general-owner@postgresql.org [mailto:pgsql-general-owner@postgresql.org] De la part de hubert depesz lubaczewski
Envoyé : July-09-14 9:55 AM
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
Also, on windows, one can use the forward slash ‘/’ instead of the backslash in a path
Just my 2 cents.
-Mark
В списке pgsql-general по дате отправления: