Re: [PATCHES] Re: [PATCH] Re: Setuid functions

From: Mark Volpe <volpe(dot)mark(at)epa(dot)gov>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Mark Volpe <volpe(dot)mark(at)epamail(dot)epa(dot)gov>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCHES] Re: [PATCH] Re: Setuid functions
Date: 2001-07-19 16:40:13
Message-ID: 3B570D6D.7F6E05E@epa.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

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.
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Howard Williams 2001-07-19 17:08:31 RELAX! - or more to the point, how do I temporarily relax a trigger/constraint?
Previous Message Mikheev, Vadim 2001-07-19 15:54:24 RE: OID wraparound (was Re: pg_depend)

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2001-07-19 17:08:52 Re: [PATCHES] Re: [PATCH] Re: Setuid functions
Previous Message Anders Bengtsson 2001-07-19 14:26:50 Re: [PATCHES] Re: [PATCH] Cleanup of JDBC character encoding