Re: Backslashes in string literals - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: Backslashes in string literals
Date
Msg-id 43F05E16.EE98.0025.0@wicourts.gov
Whole thread Raw
In response to Backslashes in string literals  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: Backslashes in string literals
List pgsql-hackers
This patch doesn't leave the standard_conforming_strings entry in guc.c
with the GUC_REPORT flag, which it needs for psql to work right.  Should
I submit one last patch with this fix and the proper "expected"
regression file?  If so, where should I send it?  (The hackers list
won't take a file as big as that patch.)

-Kevin


>>> On Sun, Feb 12, 2006 at  3:17 pm, in message
<200602122117.k1CLHuU22118@candle.pha.pa.us>, Bruce Momjian
<pgman@candle.pha.pa.us> wrote: 

> Your patch has been added to the PostgreSQL unapplied patches list
at:
> 
>     http://momjian.postgresql.org/cgi- bin/pgpatches
> 
> It will be applied as soon as one of the PostgreSQL committers
reviews
> and approves it.



pgsql-hackers by date:

Previous
From: Dave Cramer
Date:
Subject: Re: what's stored in pg_tblspc
Next
From: Tom Lane
Date:
Subject: Re: Postgresql crash (signal 11). keywords: distinct, subselect, union