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

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Hans Postma <hans(at)aeteurope(dot)nl>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2634: path requires double \\ for WAL
Date: 2006-09-18 18:26:55
Message-ID: 1158604015.30652.4.camel@dogma.v10.wvs
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2006-09-18 18:32:37 Re: BUG #2634: path requires double \\ for WAL
Previous Message Bruce Momjian 2006-09-18 17:37:21 Re: BUG #2634: path requires double \\ for WAL