| From: | Mark Volpe <volpe(dot)mark(at)epa(dot)gov> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Setuid functions |
| Date: | 2001-06-20 19:57:08 |
| Message-ID: | 3B310014.409E1733@epa.gov |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Okay, what I'm thinking is to have a pair of commands added to PL/pgSQL. For
the sake of example we'll call them:
ENABLE PRIVLEDGE --> Sets user ID to that of the function's owner
DISABLE PRIVLEDGE --> Restores the original UID
I saw something like this being used in the referential integrity code, and
thought this would be a nice (albeit incomplete) way to generalize this
ability.
Mark
Mark Volpe wrote:
>
> I know this topic was discussed a few months ago, but I'm wondering if any
> decisions have been reached on if, how, and when setuid functions and triggers
> might be implemented. If not, I have an idea to throw at it.
>
> Thanks,
> Mark
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sergio Bruder | 2001-06-20 20:30:58 | Re: PHP HOWTO v24.0 released: ADODB connects oracle, pgsql, mysql, sybase.. |
| Previous Message | Peter Eisentraut | 2001-06-20 18:42:06 | Re: [current] readline breakage |