From: eponymous alias <eponymousalias@yahoo.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: apparent loss of database access permissions
Date: Mon, 19 Sep 2022 23:56:56 +0000 (UTC)
Message-ID: <1545842961.29225.1663631816019@mail.yahoo.com> (raw)
In-Reply-To: <519733.1663618266@sss.pgh.pa.us>
References: <2085551791.33703.1663615115771.ref@mail.yahoo.com>
<2085551791.33703.1663615115771@mail.yahoo.com>
<519733.1663618266@sss.pgh.pa.us>
> 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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: eponymousalias@yahoo.com, tgl@sss.pgh.pa.us, pgsql-bugs@lists.postgresql.org
Subject: Re: apparent loss of database access permissions
In-Reply-To: <1545842961.29225.1663631816019@mail.yahoo.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox