Re: Re: [BUGS] BUG #4027: backslash escaping not disabled inplpgsql
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Cc: "Peter Eisentraut" <peter_e@gmx.net>, "Bruce Momjian" <bruce@momjian.us>, "Jonathan Guthrie" <jguthrie@brokersys.com>, "PostgreSQL-development" <pgsql-hackers@postgresql.org>
Date: 2009-04-09T16:06:16Z
Lists: pgsql-bugs, pgsql-hackers
"Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes:
> Bruce Momjian <bruce@momjian.us> wrote:
>> I think the big issue is that having standard_conforming_strings
>> affect function behavior introduces the same problems we have had in
>> the past of having a GUC affect function behavior.
> Can't that be managed with this CREATE FUNCTION option?:
> SET configuration_parameter { TO value | = value | FROM CURRENT }
It can be, the question is whether we're prepared to break everything
under the sun until people add that.
regards, tom lane