From: | darcy(at)druid(dot)net (D'Arcy J(dot)M(dot) Cain) |
---|---|
To: | maillist(at)candle(dot)pha(dot)pa(dot)us (Bruce Momjian) |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Table permissions problem |
Date: | 1998-08-13 16:13:15 |
Message-ID: | m0z7003-00006FC@druid.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Thus spake Bruce Momjian
> > > Remember some tables are shared with all databases. Makes things more
> > > difficult.
> >
> > I didn't realize that. I assume that you don't mean some system tables
> > as they could, I am sure, be special cased. Can you expand? I once
> > had a situation where a table in one database was trashed by being filled
> > with data from another table of the same name in another database. Was
> > I bitten by this feature somehow? At the same time I like the idea of
> > sharing tables. It would be perfect for things like time zone and
> > province/state tables.
>
> See pgsql/data/ and you will see the tables that are shared:
>
> pg_database
> pg_group
> pg_shadow
> pg_variable
>
> Makes sense they have to be shared.
Sure. I guess that had nothing to do with my problem then. I guess it
also means that I can't share tables myself like I mentioned. Oh well.
So could we special case these tables then and let the database owner
create views on the rest?
--
D'Arcy J.M. Cain <darcy(at){druid|vex}.net> | Democracy is three wolves
http://www.druid.net/darcy/ | and a sheep voting on
+1 416 424 2871 (DoD#0082) (eNTP) | what's for dinner.
From | Date | Subject | |
---|---|---|---|
Next Message | Jackson, DeJuan | 1998-08-13 16:15:05 | RE: [HACKERS] tuple return from function |
Previous Message | Jan Wieck | 1998-08-13 16:11:48 | Re: [HACKERS] tuple return from function |