| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | "Jonathan Guthrie" <jguthrie(at)brokersys(dot)com>, "Peter Eisentraut" <peter_e(at)gmx(dot)net>, "Bruce Momjian" <bruce(at)momjian(dot)us>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Re: [BUGS] BUG #4027: backslash escaping notdisabled inplpgsql |
| Date: | 2009-04-10 19:29:39 |
| Message-ID: | 29182.1239391779@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> Let me ask this -- If we were to change the plpgsql parser to pay
> attention to the GUC, it couldn't break anything for any environment
> which always has the GUC 'off', could it?
Right, because the behavior wouldn't actually change.
I'm starting to lean in the same direction --- the current plpgsql
behavior with the GUC 'on' is sufficiently broken that it seems unlikely
anyone is doing much with plpgsql and that setting.
It still remains that actually flipping the default would probably
provoke lots of breakage, but plpgsql's current behavior doesn't
help that.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2009-04-10 19:42:37 | Re: Re: [BUGS] BUG #4027: backslash escaping notdisabled inplpgsql |
| Previous Message | Tom Lane | 2009-04-10 19:24:16 | Re: Re: [BUGS] BUG #4027: backslash escaping notdisabled inplpgsql |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dann Corbit | 2009-04-10 19:29:59 | Re: Windows installation service |
| Previous Message | Tom Lane | 2009-04-10 19:24:16 | Re: Re: [BUGS] BUG #4027: backslash escaping notdisabled inplpgsql |