Allow pg_dumpall to work without pg_authid

From: Robins Tharakan <tharakan(at)gmail(dot)com>
To: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Allow pg_dumpall to work without pg_authid
Date: 2017-02-18 18:54:34
Message-ID: CAEP4nAz9V4H41_4ESJd1Gf0v=devkqO1=po91jUw-GJSx8Hxqg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

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.

I have a fork here (a few weeks old):
https://github.com/postgres/postgres/commit/552f4d92fde9518f934447e032b8ffcc945f12d9

Thanks
Robins Tharakan
http://www.thatguyfromdelhi.com/2016/12/custom-pgdumpall-now-works-with-aws.html
--

-
robins

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2017-02-18 21:06:41 Re: [COMMITTERS] pgsql: Add new function dsa_allocate0.
Previous Message Tom Lane 2017-02-18 18:23:30 Re: Instability in select_parallel regression test