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

From Philip Warner
Subject Re: [PATCH] Re: Setuid functions
Date
Msg-id 3.0.5.32.20010624113105.01e777f0@mail.rhyme.com.au
Whole thread Raw
In response to Re: [PATCH] Re: Setuid functions  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
At 20:47 23/06/01 -0400, Tom Lane wrote:
>Peter Eisentraut <peter_e@gmx.net> writes:
>> The term for user identity is "authorization", so I would
>> call these commands
>
>>   SET AUTHORIZATION { INVOKER | DEFINER }
>
>I like that better, too.
>

I have not read the whole thread, but I am used to module level definitions
(which easily translate to funtion level):
   Create Module ZZZ [Authorization <auth-name>]

Where <auth-name> is any valid UID or Role (we don't have roles yet). We
definitely should not limit ourselves to DEFINER or INVOKER (and obviously,
when undefined, it is CURRENT_USER). 


----------------------------------------------------------------
Philip Warner                    |     __---_____
Albatross Consulting Pty. Ltd.   |----/       -  \
(A.B.N. 75 008 659 498)          |          /(@)   ______---_
Tel: (+61) 0500 83 82 81         |                 _________  \
Fax: (+61) 0500 83 82 82         |                 ___________ |
Http://www.rhyme.com.au          |                /           \|                                |    --________--
PGP key available upon request,  |  /
and from pgp5.ai.mit.edu:11371   |/


pgsql-hackers by date:

Previous
From: Marko Kreen
Date:
Subject: Re: [PATCH] by request: base64 for bytea
Next
From: Bruce Momjian
Date:
Subject: Re: [PATCH] by request: base64 for bytea