| From: | Karel Zak <zakkr(at)zf(dot)jcu(dot)cz> |
|---|---|
| To: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
| Cc: | "'Peter Eisentraut'" <peter_e(at)gmx(dot)net>, "'PostgreSQL Development'" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: AW: Proposal for enhancements of privilege system |
| Date: | 2000-05-30 11:46:09 |
| Message-ID: | Pine.LNX.3.96.1000530132657.18344C-100000@ara.zf.jcu.cz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 30 May 2000, Zeugswetter Andreas SB wrote:
> >
> > > Other db's usually use a char array for priaction and don't have
> > > priisgrantable, but code it into priaction. Or they use a bitfield.
> > > This has the advantage of only producing one row per table.
> >
> > That's the price I'm willing to pay for abstraction,
> > extensibility, and
> > verifyability. But I'm open for better ideas.
>
> Imho this is an area that is extremly sensitive to performance,
> the rights have to be checked for each access.
Yes, but I believe that Peter's idea is good. System tables are used for
each access not only for ACL, and performance problem is a problem for
system cache not primary for privilege system.
I look forward set privilege for columns and functions. Large multiuser
projects need it.
Karel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2000-05-30 11:49:40 | Re: AW: Proposal for enhancements of privilege system |
| Previous Message | Zeugswetter Andreas SB | 2000-05-30 11:39:17 | AW: Proposal for enhancements of privilege system |