Skip site navigation (1) Skip section navigation (2)

Re: BUG #4027: backslash escaping not disabled in plpgsql

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-bugs(at)postgresql(dot)org
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Jonathan Guthrie" <jguthrie(at)brokersys(dot)com>
Subject: Re: BUG #4027: backslash escaping not disabled in plpgsql
Date: 2008-03-12 06:54:09
Message-ID: 200803120754.14367.peter_e@gmx.net (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-hackers
Tom Lane wrote:
> plpgsql does not consider standard_conforming_strings --- it still uses
> backslash escaping in its function bodies regardless.  Since the
> language itself is not standardized, I see no particular reason that
> standard_conforming_strings should govern it.

I think plpgsql should behave either consistently with the rest of PostgreSQL 
or with Oracle, which it is copied from.

> I believe the reason for 
> not changing it was that it seemed too likely to break existing
> functions, with potentially nasty consequences if they chanced to be
> security definers.

Is this actually true or did we just forget it? :-)

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2008-03-12 06:59:21
Subject: Re: BUG #4027: backslash escaping not disabled in plpgsql
Previous:From: James MansionDate: 2008-03-12 06:11:54
Subject: Build problem with VS2008 Express Edition

pgsql-bugs by date

Next:From: Tom LaneDate: 2008-03-12 06:59:21
Subject: Re: BUG #4027: backslash escaping not disabled in plpgsql
Previous:From: Tom LaneDate: 2008-03-12 06:44:40
Subject: Re: 8.3.0 backend segfaults

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group