Horton

Re: pg_auth_members.grantor is bunk

Robert Haas <robertmhaas@gmail.com>

View thread View on postgr.es
From: Robert Haas <robertmhaas@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Stephen Frost <sfrost@snowman.net>, "David G. Johnston" <david.g.johnston@gmail.com>, Mark Dilger <mark.dilger@enterprisedb.com>, Andrew Dunstan <andrew@dunslane.net>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2022-08-01T17:33:12Z
Lists: pgsql-hackers 
On Sun, Jul 31, 2022 at 2:34 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Indeed.  I've not read the patch, but I just wanted to mention that
> the cfbot shows it as failing regression tests on all platforms.
> Possibly a conflict with some recent commit?

I can't see this on cfbot - either I don't know how to use it
properly, which is quite possible, or the results aren't showing up
because of the close of the July CommitFest.

I tried a rebase locally and it didn't seem to change anything
material, not even context lines.

Can you provide a link or something that I can look at?

-- 
Robert Haas
EDB: http://www.enterprisedb.com

Commits

  1. Make role grant system more consistent with other privileges.

  2. Ensure that pg_auth_members.grantor is always valid.

  3. Remove the ability of a role to administer itself.

  4. Add tests of the CREATEROLE attribute

  5. Replace explicit PIN entries in pg_depend with an OID range test.

  6. Shore up ADMIN OPTION restrictions.

  7. Add pg_has_role() family of privilege inquiry functions modeled after the

  8. Align GRANT/REVOKE behavior more closely with the SQL spec, per discussion