Re: Backslashes in string literals

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Backslashes in string literals
Date: 2006-02-10 16:31:13
Message-ID: 200602101631.k1AGVDm04293@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Kevin Grittner wrote:
> >>> 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.
>

Oh, what I normally do is to look at regression.diff, and if that looks
OK, I just apply it to the expected file like this:

cd expected
patch < ../regression.diff

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Martijn van Oosterhout 2006-02-10 16:46:56 Re: PostgreSQL 8.0.6 crash
Previous Message Jim C. Nasby 2006-02-10 16:22:44 Re: Scrollable cursors and Sort performance