From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Where to stick function setuid |
Date: | 2000-09-17 17:52:10 |
Message-ID: | 6716.969213130@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Where were we on this? Yes/No/Maybe?
>>
>>>> Instead, when fmgr is setting up to call a setuid function, have it
>>>> insert an extra level of function handler that does the
>>>> save/setup/restore of current UID.
>>
>> I don't quite understand. Do you mean like a PL function handler? But then
>> this thing wouldn't work for external PL's unless we either have a setuid
>> version of each or have nested handlers.
Sorry, I forgot to reply. Nested handlers were exactly what I was
advocating. Or more accurately, *a* nested handler; you'd only need
one regardless of the target function's language. I'm envisioning
that it'd have fn_extra pointing at a block that contains the UID to
be used for the call and the FmgrInfo for the underlying function.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-09-17 18:18:54 | Re: ascii to character conversion in postgres |
Previous Message | Tom Lane | 2000-09-17 17:48:37 | Re: broken locale in 7.0.2 without multibyte support (FreeBSD 4.1-RELEASE) ? |