Horton
Menu

Re: Re: [BUGS] BUG #4027: backslash escaping notdisabled inplpgsql

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Cc: "Jonathan Guthrie" <jguthrie@brokersys.com>, "Peter Eisentraut" <peter_e@gmx.net>, "Bruce Momjian" <bruce@momjian.us>, "PostgreSQL-development" <pgsql-hackers@postgresql.org>
Date: 2009-04-10T18:57:10Z
Lists: pgsql-bugs, pgsql-hackers 
"Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes:
> The aspect of 8.3 behavior that concerns me most is that neither the
> author of a function, nor anyone using it, can control or predict
> which way a string literal with a backslash will be interpreted,
> unless the author explicitly specifies the SET
> standard_conforming_strings clause in the function declaration.

Yeah.  This is one reason why I'm still afraid to flip the default
value of standard_conforming_strings --- there seems too much risk
of widespread breakage.

I don't have a good solution for it, but I agree it's a problem.

			regards, tom lane