From: | Melvin Call <melvincall979(at)gmail(dot)com> |
---|---|
To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Understanding database schemas |
Date: | 2013-08-02 18:52:13 |
Message-ID: | CADGQN565kEhRCjB-rhMA2ms73BWDo2hy8Z1zNvtEoF9v-M=TVw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Aug 2, 2013 at 1:36 PM, Bosco Rama <postgres(at)boscorama(dot)com> wrote:
> On 08/02/13 10:56, Melvin Call wrote:
> >
> > If I may pigtail another related question, what is the procedure for
> > allowing another user access to that schema?
>
> Heh. You almost have the words already:
> grant usage on schema hrschema to hr_user;
>
Too easy! Thanks for the help. That'll teach me to try to learn something
new in the middle of development crunch time! And many thanks for the link
as well. This will help a great deal.
>
> This will allow them to see the objects in the schema. It does nothing
> to allow them to access the objects themselves, so you'll still need to
> grant the appropriate privileges on the objects within the schema. You
> can use default privileges if you don't wish to grant them at creation
> time. See the docs for default privs:
>
> <http://www.postgresql.org/docs/9.2/static/sql-alterdefaultprivileges.html
> >
>
> HTH,
> Bosco.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2013-08-02 19:08:47 | Re: demystifying nested loop vs. merge join query plan choice |
Previous Message | Bosco Rama | 2013-08-02 18:36:56 | Re: Understanding database schemas |