Horton
Menu

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

Josh Berkus <josh@agliodbs.com>

View thread
From: Josh Berkus <josh@agliodbs.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Bruce Momjian <bruce@momjian.us>, Brendan Jurd <direvus@gmail.com>, Kevin Grittner <Kevin.Grittner@wicourts.gov>, Jonathan Guthrie <jguthrie@brokersys.com>, Peter Eisentraut <peter_e@gmx.net>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2009-04-10T20:35:06Z
Lists: pgsql-bugs, pgsql-hackers 
Tom,

> Actually, what this thread is leading me towards is the idea that almost
> nobody really has standard_conforming_strings turned on in production
> (except maybe with apps ported from Oracle or someplace else).  If they
> did, we'd be seeing more complaints about plpgsql not working properly.
> So maybe we *could* change plpgsql to honor the GUC without anyone
> noticing too much.

Actually, a lot of people are using $escapes$ for all nested quotes in 
plpgsql.  So they wouldn't notice the problem.

-- 
Josh Berkus
PostgreSQL Experts Inc.
www.pgexperts.com