Re: Re: [BUGS] BUG #4027: backslash escapingnotdisabled inplpgsql
Bruce Momjian <bruce@momjian.us>
From: Bruce Momjian <bruce@momjian.us>
To: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Jonathan Guthrie <jguthrie@brokersys.com>, Peter Eisentraut <peter_e@gmx.net>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2009-04-10T19:56:02Z
Lists: pgsql-bugs, 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. +