Re: Re: [BUGS] BUG #4027: backslash escapingnotdisabled inplpgsql - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Re: [BUGS] BUG #4027: backslash escapingnotdisabled inplpgsql
Date
Msg-id 1304.1239398174@sss.pgh.pa.us
Whole thread Raw
In response to Re: Re: [BUGS] BUG #4027: backslash escapingnotdisabled inplpgsql  (Andrew Gierth <andrew@tao11.riddles.org.uk>)
List 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


pgsql-hackers by date:

Previous
From: Dave Page
Date:
Subject: Re: Windows installation service
Next
From: Tom Lane
Date:
Subject: Re: Re: [BUGS] BUG #4027: backslash escapingnotdisabledinplpgsql