Re: Re: [BUGS] BUG #4027: backslash escaping not disabled inplpgsql - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Re: [BUGS] BUG #4027: backslash escaping not disabled inplpgsql
Date
Msg-id 16095.1239293176@sss.pgh.pa.us
Whole thread Raw
In response to Re: [BUGS] BUG #4027: backslash escaping not disabled inplpgsql  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: Re: [BUGS] BUG #4027: backslash escaping not disabled inplpgsql  (Bruce Momjian <bruce@momjian.us>)
Re: Re: [BUGS] BUG #4027: backslash escaping not disabled inplpgsql  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List 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


pgsql-hackers by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: [BUGS] BUG #4027: backslash escaping not disabled inplpgsql
Next
From: Bruce Momjian
Date:
Subject: Re: Re: [BUGS] BUG #4027: backslash escaping not disabled inplpgsql