From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Brendan Jurd <direvus(at)gmail(dot)com>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Jonathan Guthrie <jguthrie(at)brokersys(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Re: [BUGS] BUG #4027: backslash escaping notdisabled inplpgsql |
Date: | 2009-04-10 20:35:06 |
Message-ID: | 49DFAD7A.9010507@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Gierth | 2009-04-10 20:38:27 | Re: Re: [BUGS] BUG #4027: backslash escapingnotdisabled inplpgsql |
Previous Message | Euler Taveira de Oliveira | 2009-04-10 20:32:43 | Re: libpq 8.4 beta1: $PGHOST complains about missing root.crt |
From | Date | Subject | |
---|---|---|---|
Next Message | l0rins | 2009-04-10 20:37:22 | Re: unable to install tsearch2 on PostgreSQL 8.3.7 successfully |
Previous Message | David E. Wheeler | 2009-04-10 20:31:51 | Re: A renewed plea for inclusion of zone.tab |