> Date: Sat, 30 Nov 2002 23:14:43 -0500
> From: Tom Lane <tgl@sss.pgh.pa.us>
>
> Jochem van Dieten <jochemd@oli.tudelft.nl> writes:
> > Tom Lane wrote:
> >> This has nothing to do with USAGE on the schema; it is just a matter of
> >> being able to read the system catalogs.
>
> > <quote>
> > By default, users cannot see the objects in schemas they do not own.
> > </quote>
>
>
> I agree that this isn't completely ideal, but I stand by my comment that
> it's not worth breaking every client that looks at system catalogs in
> order to prevent it.
>
What about the following scenario:
- move the information in pg_class etc. to new tables pg_dba_class etc.
to which only DBAs have access
- redefine pg_class etc. as views which contain only the information the specific
user has right to see
This mimics the way Oracle's data dictionary works and yet would not break existing
clients because the objects pg_class etc. still exist (though containing less data
for less privileged users).
Christoph Dalitz