| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jonathan Guthrie <jguthrie(at)brokersys(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Re: [BUGS] BUG #4027: backslash escapingnotdisabled inplpgsql |
| Date: | 2009-04-10 19:56:02 |
| Message-ID: | 200904101956.n3AJu2m23881@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Kevin Grittner wrote:
> Bruce Momjian <bruce(at)momjian(dot)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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2009-04-10 19:57:51 | Re: libpq 8.4 beta1: $PGHOST complains about missing root.crt |
| Previous Message | Kevin Grittner | 2009-04-10 19:54:12 | Re: Re: [BUGS] BUG #4027: backslash escapingnotdisabled inplpgsql |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-04-10 20:07:17 | Re: Re: [BUGS] BUG #4027: backslash escapingnotdisabled inplpgsql |
| Previous Message | Kevin Grittner | 2009-04-10 19:54:12 | Re: Re: [BUGS] BUG #4027: backslash escapingnotdisabled inplpgsql |