Re: [HACKERS] Allow pg_dumpall to work without pg_authid - Mailing list pgsql-hackers

From Stephen Frost
Subject Re: [HACKERS] Allow pg_dumpall to work without pg_authid
Date
Msg-id 20170218230833.GA9812@tamriel.snowman.net
Whole thread Raw
In response to [HACKERS] Allow pg_dumpall to work without pg_authid  (Robins Tharakan <tharakan@gmail.com>)
Responses Re: [HACKERS] Allow pg_dumpall to work without pg_authid  (Robins Tharakan <tharakan@gmail.com>)
List pgsql-hackers
Greetings,

* Robins Tharakan (tharakan@gmail.com) wrote:
> I would like to work on a patch to accommodate restricted environments
> (such as AWS RDS Postgres) which don't allow pg_authid access since their
> definition of Superuser is just a regular user with extra permissions.
>
> Would you consider a patch to add a flag to work around this restriction,
> Or, do you prefer that this be maintained outside core?
>
> I could add a flag such as --avoid-pgauthid (am open to options) that skips
> pg_authid and uses pg_user (but essentially resets all User passwords).
> Mostly this is better than not being able to get the dump at all.

If anything, it should use pg_roles, not pg_user.

I don't really like the "--avoid-pgauthid" option, but "--no-passwords"
would probably work.

In general, this seems like a reasonable thing to add support for.

Thanks!

Stephen

pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: [HACKERS] logical replication access control patches
Next
From: Thomas Munro
Date:
Subject: Re: [HACKERS] [COMMITTERS] pgsql: Add new function dsa_allocate0.