| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Edwin UY <edwin(dot)uy(at)gmail(dot)com> |
| Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: GRANT USAGE ON SCHEMA |
| Date: | 2025-06-14 23:19:06 |
| Message-ID: | CAKFQuwY8+JZe1KDh25LrqxbKNe-sVp265K5vFdzMXG1EHOcmhw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Sat, Jun 14, 2025 at 3:09 PM Edwin UY <edwin(dot)uy(at)gmail(dot)com> wrote:
> I thought it was supposed to all 'full' access of one schema to the other
>
Where did you get the idea that objects (aside from roles) ever get
privileges on other objects? Or did you also create roles "a" and "b" and
are just using the wrong terminology here?
There is also no such thing as permissions on one type of object somehow
affecting your privileges on other object types. Your privileges on
schemas will not influence (directly) your permissions on tables. Neither
to grant additional privileges or to block them - say if you don't have
usage on schema but do have select on a contained table. Corner-cases that
do behave this way notwithstanding - it isn't reliable.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kushal Shri | 2025-06-15 10:05:27 | Re: PostgreSQL Upgrade (v9.5 to v12) with Django 2.0 |
| Previous Message | Tom Lane | 2025-06-14 22:29:04 | Re: GRANT USAGE ON SCHEMA |