Re: [PATCH] Re: Setuid functions

From: Philip Warner <pjw(at)rhyme(dot)com(dot)au>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Mark Volpe <volpe(dot)mark(at)epa(dot)gov>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCH] Re: Setuid functions
Date: 2001-06-24 01:31:05
Message-ID: 3.0.5.32.20010624113105.01e777f0@mail.rhyme.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At 20:47 23/06/01 -0400, Tom Lane wrote:
>Peter Eisentraut <peter_e(at)gmx(dot)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 |/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2001-06-24 02:37:29 Re: [PATCH] by request: base64 for bytea
Previous Message Rod Taylor 2001-06-24 01:18:01 Postgres to Dia UML