Re: Controlling changes in plpgsql variable resolution - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: Controlling changes in plpgsql variable resolution
Date
Msg-id 4ADF68D5.8000404@agliodbs.com
Whole thread Raw
In response to Re: Controlling changes in plpgsql variable resolution  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Controlling changes in plpgsql variable resolution
Re: Controlling changes in plpgsql variable resolution
List pgsql-hackers
> That's what the #option alternative is for.  Yes, it's a bit ugly, but
> it's perfectly functional, and secure too.

I still don't see why it's needed.  If the function owner simply sets
the option in the function definitions (as a userset), it doesn't matter
what the calling user sets, does it?

All that's needed is a scripting example to set this in all function
definitions as a regular setting.

--Josh Berkus




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Controlling changes in plpgsql variable resolution
Next
From: Heikki Linnakangas
Date:
Subject: Re: Hot standby, prepared xacts, locks