Re: [PATCHES] Re: [PATCH] Re: Setuid functions - Mailing list pgsql-hackers

From Mark Volpe
Subject Re: [PATCHES] Re: [PATCH] Re: Setuid functions
Date
Msg-id 3B570D6D.7F6E05E@epa.gov
Whole thread Raw
In response to Re: [PATCHES] Re: [PATCH] Re: Setuid functions  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: [PATCHES] Re: [PATCH] Re: Setuid functions  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
OK, I finally got around to adding the superuser check to my patch. So I try
to test it and...

ERROR:  Only users with Postgres superuser privilege are permitted to create a
function in the 'plpgsql' language.

D'oh! So, if this is the case, then the last patch should be fine after all.

Mark

Peter Eisentraut wrote:
> 
> If you mean "only allow a superuser do define functions using this
> mechanism", that could work.  But it would probably make this feature a
> lot less attractive, because any setuid function would have to run with
> super powers.
>


pgsql-hackers by date:

Previous
From: "Mikheev, Vadim"
Date:
Subject: RE: OID wraparound (was Re: pg_depend)
Next
From: Tom Lane
Date:
Subject: Re: [PATCHES] Re: [PATCH] Re: Setuid functions