Re: Getting rid of pg_pltemplate - Mailing list pgsql-hackers

From Christopher Browne
Subject Re: Getting rid of pg_pltemplate
Date
Msg-id CAFNqd5XUFJuK0Na5fGuo3eJvfWbjR_rB_pO6Vye51AzKiiGLUw@mail.gmail.com
Whole thread Raw
In response to Re: Getting rid of pg_pltemplate  (Dimitri Fontaine <dimitri@2ndQuadrant.fr>)
Responses Re: Getting rid of pg_pltemplate
List pgsql-hackers
On Tue, Aug 23, 2011 at 3:09 PM, Dimitri Fontaine
<dimitri@2ndquadrant.fr> wrote:
> Tom Lane <tgl@sss.pgh.pa.us> writes:
>> We'll add a new boolean parameter to extension control files, called say
>> "dba_create" (ideas for better names welcome).  If it's missing or set
>> to false, there's no change in behavior.  When it's true, then
>>
>> (a) you must be superuser or owner of the current database to create the
>> extension;
>>
>> (b) the commands within the extension's script will be run as though by a
>> superuser, even if you aren't one.
>
> That's called sudo on linux.  I propose that we stick to such a name.

Actually, this is somewhat more like UNIX setuid (2).

When I first started using SECURITY DEFINER functions, I thought of it
as being "like sudo."  But it's really "like setuid".
--
When confronted by a difficult problem, solve it by reducing it to the
question, "How would the Lone Ranger handle this?"


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Getting rid of pg_pltemplate
Next
From: Andrew Dunstan
Date:
Subject: pg_dump --exclude-table-data