Re: Per-function search_path => per-function GUC settings

On Sep 1, 2007, at 1:36 PM, Brendan Jurd wrote:

> So if we integrated the GUC settings into CREATE FUNCTION, we'd end up
> writing something like
>
> CREATE FUNCTION foo(int) RETURNS int AS $$
> ...
> $$
>  LANGUAGE plpgsql
>  STABLE
>  STRICT
>  SECURITY DEFINER
>  RESET search_path
>  SET regex_flavor = 'cinnamon';
>
> That doesn't seem especially horrible.  In what way do you feel it is
> inconsistent with existing syntax?


I like this and would really like to see way to set everything using  
CREATE FUNCTION. Using ALTER only requires maintaining a separate  
copy of of function arguments which can be a hassle for large  
argument lists.




John DeSoi, Ph.D.
http://pgedit.com/
Power Tools for PostgreSQL