From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | rameshparnanditech(at)gmail(dot)com |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #10817: archive settings |
Date: | 2014-06-30 20:14:13 |
Message-ID: | CAB7nPqRgVFPAXPvbB1cNxrO4=8t9nekmS5us+K9Q0L69WzezKA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Mon, Jun 30, 2014 at 10:01 PM, <rameshparnanditech(at)gmail(dot)com> wrote:
> when try to set archive_command in postgres.conf
>
This is not a bug, it is better to ask such questions in pgsql-general or
pgsql-novice.
> like,
> archive_command = 'copy "%p" "C:\Program Files\PostgreSQL\9.3\testdata\%f"'
>
I recall that the use of double backslash "\\" is necessary to indicate the
folder path, making the command look like that actually:
archive_command = 'copy "%p" "C:\\Program
Files\\PostgreSQL\\9.3\\testdata\\%f"'
then ran this query pg_stop_backup(); its return error like,
> wait for wal segments to archive 60 seconds please check archive command..
> following error retunrs
>
Without more details about the failure, we cannot guess what is happening?
Is it a permission issue? Does the target folder exist?
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2014-07-01 01:49:17 | Re: pg_upgrade < 9.3 -> >=9.3 misses a step around multixacts |
Previous Message | Tom Lane | 2014-06-30 14:16:57 | Re: BUG #10816: explain analyze reports different rows counts before and after sort |