Re: Controlling changes in plpgsql variable resolution

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Controlling changes in plpgsql variable resolution
Date: 2009-10-21 20:02:29
Message-ID: 4ADF68D5.8000404@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2009-10-21 20:02:43 Re: Hot standby, prepared xacts, locks
Previous Message Tom Lane 2009-10-21 19:38:04 Re: Controlling changes in plpgsql variable resolution