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

From Robert Haas
Subject Re: [HACKERS] Allow pg_dumpall to work without pg_authid
Date
Msg-id CA+TgmoaZ1D59xWMHi+061cKDn6FwUspG1i-7L8aHiF86Y9tRZQ@mail.gmail.com
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>)
Re: [HACKERS] Allow pg_dumpall to work without pg_authid  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
On Sun, Feb 19, 2017 at 12:24 AM, 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 am a little surprised that this patch has gotten such a good
reception.  We haven't in the past been all that willing to accept
core changes for the benefit of forks of PostgreSQL; extensions, sure,
but forks?  Maybe we should take the view that Amazon has broken this
and Amazon ought to fix it, rather than making it our job to (try to)
work around their bugs.

On the other hand, maybe that approach is narrow-minded.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] Reduce lock levels for reloptions
Next
From: Robert Haas
Date:
Subject: Re: [HACKERS] Patch: Write Amplification Reduction Method (WARM)