Re: Backslashes in string literals

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Backslashes in string literals
Date: 2006-02-10 15:48:20
Message-ID: 43EC6164.EE98.0025.0@wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>>> On Thu, Feb 9, 2006 at 10:31 pm, in message
<200602100431(dot)k1A4VlY21635(at)candle(dot)pha(dot)pa(dot)us>, Bruce Momjian
<pgman(at)candle(dot)pha(dot)pa(dot)us> wrote:
>
> OK, I got it working. The fix is to add GUC_REPORT to guc.c for
> standard_conforming_strings. See the same flag on
> session_authorization. That will cause libpq to see any changes made
to
> that variable. Sorry I didn't know that detail before.

Fantastic! I added that flag on my end, and everything I've tried is
working perfectly, except: I found that I didn't get my "expected" file
100% right with my hand-crafted attempt. You're probably already on
that, but just in case it might save you a few minutes -- attached is a
good patch for the "expected" file to go with the new regression test
script for strings.

-Kevin

Attachment Content-Type Size
strings.out.patch application/octet-stream 4.6 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2006-02-10 15:54:36 Re: FW: PGBuildfarm member snake Branch HEAD Status changed
Previous Message ohp 2006-02-10 15:44:31 Re: how is that possible