From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Marc Munro <marc(at)bloodnok(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: row based security ... was Different views with same name for |
Date: | 2002-01-21 20:19:20 |
Message-ID: | 10815.1011644360@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Marc Munro <marc(at)bloodnok(dot)com> writes:
> For this, we need to be able to have functions which run with the
> permissions of the rule owner rather than the caller (please see my
> response, in plsql-general, to depesz(at)depesz(dot)pl, Re: IDEA: "suid"
> function).
I believe "suid" functions are a more practical solution than expecting
the rule mechanism to handle this for you. I don't want to put access
checking/id switching overhead into the basic expression evaluation
engine; but it's hard to see how we could make functions-invoked-in-rules
be treated specially without that. The problem is that expressions
coming out of the rewriter might be arbitrary combinations of clauses
that appeared in the rule and clauses that appeared in the user's
original query.
"Suid" functions have been on the TODO list for awhile. Peter E. has
been making noises recently suggesting that he's actually planning to
make them happen for 7.3.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Philip Hallstrom | 2002-01-21 20:39:11 | Re: [HACKERS] PostgreSQL Licence: GNU/GPL |
Previous Message | Bruce Momjian | 2002-01-21 20:03:13 | Re: row based security ... was Different views with same name |