| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Re: [BUGS] BUG #4027: backslash escapingnotdisabled inplpgsql |
| Date: | 2009-04-10 21:16:14 |
| Message-ID: | 1304.1239398174@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> writes:
> "Tom" == Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> Tom> Back to the point at hand: do we want to look at making plpgsql
> Tom> respect the GUC?
> Surely what matters is the value of the GUC at the time that you did
> the CREATE FUNCTION, not the value at the time you happen to be
> calling it?
No, it isn't, and that's not the immediate problem anyway --- the
immediate problem is that plpgsql doesn't respect *any* value of
the GUC.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-04-10 21:24:17 | Re: Re: [BUGS] BUG #4027: backslash escapingnotdisabledinplpgsql |
| Previous Message | Kevin Grittner | 2009-04-10 20:46:09 | Re: Re: [BUGS] BUG #4027: backslash escapingnotdisabledinplpgsql |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-04-10 21:24:17 | Re: Re: [BUGS] BUG #4027: backslash escapingnotdisabledinplpgsql |
| Previous Message | Dave Page | 2009-04-10 20:58:09 | Re: Windows installation service |