From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | "Peter Eisentraut" <peter_e(at)gmx(dot)net>, "Bruce Momjian" <bruce(at)momjian(dot)us>, "Jonathan Guthrie" <jguthrie(at)brokersys(dot)com>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Re: [BUGS] BUG #4027: backslash escaping not disabled inplpgsql |
Date: | 2009-04-09 16:06:16 |
Message-ID: | 16095.1239293176@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> Bruce Momjian <bruce(at)momjian(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2009-04-09 16:18:32 | Re: Re: [BUGS] BUG #4027: backslash escaping not disabled inplpgsql |
Previous Message | Kevin Grittner | 2009-04-09 15:36:23 | Re: [BUGS] BUG #4027: backslash escaping not disabled inplpgsql |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2009-04-09 16:18:32 | Re: Re: [BUGS] BUG #4027: backslash escaping not disabled inplpgsql |
Previous Message | Kevin Grittner | 2009-04-09 15:36:23 | Re: [BUGS] BUG #4027: backslash escaping not disabled inplpgsql |