Re: Including PL/PgSQL by default - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Including PL/PgSQL by default
Date
Msg-id 4729.1203698753@sss.pgh.pa.us
Whole thread Raw
In response to Re: Including PL/PgSQL by default  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Including PL/PgSQL by default
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> Roberts, Jon wrote:
>> However, you can not create anything in Oracle without being given
>> permission to create it.  The notion that you can create a function
>> because you have connect rights to the database is foreign to me.
>> Connect should mean connect, not connect AND create.

> You'd need more than that.

> For example, since we don't support temp functions, we should probably 
> ban the creation of functions in temp schemas (which I found was possible).

What for?  If you don't want someone to use a language, you should
either revoke his USAGE privilege on that language, or remove it
from his database altogether.  We have plenty of access-control
mechanisms in place already, we don't need weird special-case
restrictions on top of those.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Linking backend in one piece
Next
From: Tom Lane
Date:
Subject: Re: Linking backend in one piece