Re: Fixing insecure security definer functions - Mailing list pgsql-hackers

From Merlin Moncure
Subject Re: Fixing insecure security definer functions
Date
Msg-id b42b73150702151044h59be9c78qebcb861459d11345@mail.gmail.com
Whole thread Raw
In response to Re: Fixing insecure security definer functions  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Fixing insecure security definer functions
List pgsql-hackers
On 2/13/07, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> I would suggest that the search path be added as an explicit parameter
> to CREATE FUNCTION, with a default of the current setting.  The main
> reason for this is that it's going to be a real PITA for pg_dump if we
> don't allow an explicit specification.

yikes!

If you guys go through with forcing functions to attach to objects
when they are created, it will break almost every project I've ever
worked on :(.  The schema/function combo fits into all kinds of de
facto partitioning strategies and organization methods.

I can understand invalidating plans when the search_path changes, though.

merlin


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Visual C++ function issues
Next
From: Tom Dunstan
Date:
Subject: Re: "anyelement2" pseudotype