Re: apparent loss of database access permissions - Mailing list pgsql-bugs

From eponymous alias
Subject Re: apparent loss of database access permissions
Date
Msg-id 1545842961.29225.1663631816019@mail.yahoo.com
Whole thread Raw
In response to Re: apparent loss of database access permissions  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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.

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: apparent loss of database access permissions
Next
From: Jeff Janes
Date:
Subject: Re: BUG #17618: unnecessary filter column <> text even after adding index