| From: | eponymous alias <eponymousalias(at)yahoo(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: apparent loss of database access permissions |
| Date: | 2022-09-19 23:56:56 |
| Message-ID: | 1545842961.29225.1663631816019@mail.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> The reason it gets to be like that is that normal grant and revoke
> operations don't make any effort to reset the ACL field to null if
> the end result of a series of operations chances to be equivalent
> to the default. However, for reasons of its own pg_dump has to
> compute the set of GRANT/REVOKE commands to issue to get from the
> default state to the object's current state --- and in this situation
> that list is empty. So no commands are issued, the ACL stays null, ...
>
> That's not a bug, just an implementation artifact.
Okay, thanks for the quick and detailed response.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2022-09-20 17:12:03 | Re: BUG #17618: unnecessary filter column <> text even after adding index |
| Previous Message | Tom Lane | 2022-09-19 20:11:06 | Re: apparent loss of database access permissions |