From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
---|---|
To: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | jwieck(at)debis(dot)com, hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/bin/initdb initdb.sh' |
Date: | 1998-02-23 20:23:54 |
Message-ID: | Pine.NEB.3.95.980223152306.17896c-100000@hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, 23 Feb 1998, Bruce Momjian wrote:
> >
> > >
> > > >
> > > > Update of /usr/local/cvsroot/pgsql/src/bin/initdb
> > > > In directory hub.org:/tmp/cvs-serv23999/bin/initdb
> > > >
> > > > Modified Files:
> > > > initdb.sh
> > > > Log Message:
> > > >
> > > > Modify initdb.sh so that it makes pg_user readable through view db_user
> > > > Modify psql so that it uses db_user instead of pg_user
> > > > GRANT SELECT on pg_class
> > >
> > > I don't know if I like the new name db_user? What do other people
> > > think? I thought pg_user_no_pwd would be nice.
> >
> >
> > create view pg_users as ...
> > ERROR: Illegal class name: pg_users -- pg_ is reserved for system catalogs
>
> Oops, yep.
>
> I guess I just liked that the pg_ stuff was all system stuff. Do you
> get this error when creating it from postgres, as initdb does? That
> would be a solution. Worked here.
My thought was more splitting the difference between a system
table (pg_) vs system view (db_) *shrug* Okay, I was grasping here :)
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 1998-02-23 20:25:48 | Re: [HACKERS] Views on aggregates - need assistence |
Previous Message | The Hermit Hacker | 1998-02-23 20:22:22 | Re: [HACKERS] Views on aggregates - need assistence |