From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | scrappy(at)hub(dot)org (The Hermit Hacker) |
Cc: | brandys(at)eng3(dot)hep(dot)uiuc(dot)edu, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Re: New pg_pwd patch and stuff |
Date: | 1998-01-15 20:51:34 |
Message-ID: | 199801152051.PAA15839@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>
>
> I wish ppl would quite dropping off CC's :( Especially when this stuff
> *should* be being discussed in pgsql-hackers(at)postgresql(dot)org(dot)(dot)(dot)
>
> As for the pg_privileges relation and whatnot...is this something we want
> for v6.3 (can it be done in 2weeks?) or wait until after v6.3 is released?
>
Well, I can create the table quite easily. The issue is what type of
flack we will get by haveing pg_user non-readable, and removing the user
name from psql's \d output.
>
>
> On Thu, 15 Jan 1998, todd brandys wrote:
>
> > > wouldn't that pose a problem with setting up someone other the
> > > the superuser to create databases? *Raised eyebrows*
> >
> > Again I feel that PostgreSQL should have a pg_privileges relation which would
> > handle the CREATE DATABASE privilege. There would be no problem then.
> >
> > Todd A. Brandys
> > brandys(at)eng3(dot)hep(dot)uiuc(dot)edu
> >
>
>
>
--
Bruce Momjian
maillist(at)candle(dot)pha(dot)pa(dot)us
From | Date | Subject | |
---|---|---|---|
Next Message | De Clarke | 1998-01-15 20:53:00 | CBAC (content based access control), OIDs, auto fields |
Previous Message | todd brandys | 1998-01-15 20:42:31 | subscribe |