BUG #2634: path requires double \\ for WAL archiving

Hans Postma wrote:

The following bug has been logged online:

Bug reference: 2634
Logged by: Hans Postma
Email address: hans@aeteurope.nl
PostgreSQL version: 8.1
Operating system: Windows XP VM virtual server
Description: path requires double \\ for WAL archiving
Details:

Hi there
Trying to use WAL-archiving, I discovered that to decribe the path where I
want the copies of the WAL-file to go, I need to enter the following in the
PostgreSQL.conf file:

archive_command = 'copy "%p" C:\\<folder>\\" %f" '

I am using a Windows 2000 (version 5 SP4) virtual server (VM 5.0.0 build
13124) running on Windows XP.

yours, Hans Postma

Yes, this is required because we use backslashes for escapes. The
backslashing can be turned off in 8.2.

--
Bruce Momjian bruce@momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

On Mon, 2006-09-18 at 13:37 -0400, Bruce Momjian wrote:

Yes, this is required because we use backslashes for escapes. The
backslashing can be turned off in 8.2.

So the postgresql.conf setting "standard_conforming strings" that turns
off backslash escaping affects the interpretation of other
postgresql.conf settings?

What if you have a path set for archive_command and then you change the
standard_conforming_strings GUC and SIGHUP the server? Will the path be
incorrect?

Regards,
Jeff Davis

Jeff Davis <pgsql@j-davis.com> writes:

So the postgresql.conf setting "standard_conforming strings" that turns
off backslash escaping affects the interpretation of other
postgresql.conf settings?

No, it doesn't. Backslashes are still escapes within postgresql.conf.

regards, tom lane