Re: Re: [BUGS] BUG #4027: backslash escapingnotdisabled inplpgsql
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Gierth <andrew@tao11.riddles.org.uk>
Cc: pgsql-hackers@postgresql.org
Date: 2009-04-10T21:16:14Z
Lists: pgsql-bugs, pgsql-hackers
Andrew Gierth <andrew@tao11.riddles.org.uk> writes: > "Tom" == Tom Lane <tgl@sss.pgh.pa.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