| From: | Pavel Luzanov <p(dot)luzanov(at)postgrespro(dot)ru> |
|---|---|
| To: | Dominique Devienne <ddevienne(at)gmail(dot)com>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | Lok P <loknath(dot)73(at)gmail(dot)com>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Users and object privileges maintenance |
| Date: | 2024-02-18 14:27:09 |
| Message-ID: | 459ef527-5d83-4bed-90d5-4bbabc1da91c@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 18.02.2024 15:19, Dominique Devienne wrote:
> On Sun, Feb 18, 2024 at 12:30 PM Laurenz Albe
> <laurenz(dot)albe(at)cybertec(dot)at> wrote:
>
> 2. In PostgreSQL, there is the important concept of ownership,
> which is not tied to the schema.
> The owner is the user who created the object.
>
>
> Personally I find that confusing. I wouldn't mind schema objects all
> belonging to the one owner.
> Or being to enforce that, as an opt-in option. Not sure what's the
> benefits of different owners for a schemas objects are.
The situation is even more confusing :-)
Roles with membership in object owner role acts as an owner.
For example they can modify or drop object or grant/revoke access to object.
--
Pavel Luzanov
Postgres Professional:https://postgrespro.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dominique Devienne | 2024-02-18 14:40:04 | Re: Users and object privileges maintenance |
| Previous Message | Dominique Devienne | 2024-02-18 12:19:32 | Re: Users and object privileges maintenance |