Re: Re: [BUGS] BUG #4027: backslash escapingnotdisabled inplpgsql - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Re: [BUGS] BUG #4027: backslash escapingnotdisabled inplpgsql
Date
Msg-id 200904101956.n3AJu2m23881@momjian.us
Whole thread Raw
In response to Re: Re: [BUGS] BUG #4027: backslash escapingnotdisabled inplpgsql  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: Re: [BUGS] BUG #4027: backslash escapingnotdisabled inplpgsql  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Kevin Grittner wrote:
> Bruce Momjian <bruce@momjian.us> wrote:
> > It would be nice to know if we are ever going to set
> > standard_conforming_strings to on.
>  
> My personal bias is to go to the standard behavior as the default at
> some point.  For legacy reasons, I don't know that you would ever want
> to remove the setting; especially since I don't think it adds much
> code if you're going to support the E'...' literals.  The ugliest
> thing about this GUC is that it adds some complications to the flex
> code, but it doesn't seem that bad to me.

Agreed, we would probably never remove standard_conforming_strings.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: Re: [BUGS] BUG #4027: backslash escapingnotdisabled inplpgsql
Next
From: Tom Lane
Date:
Subject: Re: Re: [BUGS] BUG #4027: backslash escapingnotdisabled inplpgsql