| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-bugs(at)postgresql(dot)org, "Jonathan Guthrie" <jguthrie(at)brokersys(dot)com> |
| Subject: | Re: BUG #4027: backslash escaping not disabled in plpgsql |
| Date: | 2008-03-12 06:59:21 |
| Message-ID: | 13859.1205305161@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Tom Lane wrote:
>> 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? :-)
I recall thinking about the point. The decision could've been wrong ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2008-03-12 08:25:55 | Re: BUG #4025: wsock32.dll not found |
| Previous Message | Peter Eisentraut | 2008-03-12 06:54:09 | Re: BUG #4027: backslash escaping not disabled in plpgsql |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | James Mansion | 2008-03-12 07:21:50 | Noob Hints on testing and debugging? |
| Previous Message | Peter Eisentraut | 2008-03-12 06:54:09 | Re: BUG #4027: backslash escaping not disabled in plpgsql |