Re: Schemas and access

From: <btober(at)seaworthysys(dot)com>
To: <felix-lists(at)crowfix(dot)com>
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: Re: Schemas and access
Date: 2003-06-22 22:43:21
Message-ID: 65089.66.212.203.144.1056321801.squirrel@$HOSTNAME
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> I am just beginning to investigate schemas, and have run into a
> problem. Searching the mailing lists and documentation doesn't help.
>
> This is 7.3.3 on Linux, kernel 2.4.21, good ole Slackware, compiled
> from source.
>
> Two users, JoeBob and MaryJo. JoeBob has schema xyzzy with table
> plugh. JoeBob has run
>
> GRANT SELECT on xyzzy.plugh TO public;
>
> JoeBob and MaryJo can both show permissions:
>
> joebob=> \z zyzzy.*
> Access privileges for database "joebob"
> Schema | Table | Access privileges
> --------+--------+--------------------
> xyzzy | plugh | {=r,joebob=arwdRxt}
>
> JoeBob can do anything with the table, that works. But MaryJo can't
> even select:
>
> joebob=> select * from xyzzy.plugh;
> ERROR: xyzzy: permission denied
>
> It sure looks like the schema itself is invisible to MaryJo, but
> MaryJo can run \dt xyzzy.* perfectly fine.

I think there is a "greant usage on schema" type statement that you
probably need.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2003-06-22 22:45:53 Re: Aggregate functions on ordered data?
Previous Message Tom Lane 2003-06-22 22:41:17 Re: Schemas and access