Re: Allow pg_dumpall to work without pg_authid

From: Robins Tharakan <tharakan(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Allow pg_dumpall to work without pg_authid
Date: 2017-02-26 10:59:15
Message-ID: CAEP4nAx-GA=5=YjVub-8SZ=OP+iPUU1oQDLCp2ja8+Vq3NMP-Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 26 February 2017 at 21:37, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:

>
> How's that not a bug? I mean, it's reasonable for someone to want to
> restrict the superuser in a cloud environment, but if they restrict it
> so much that you can't take a backup with standard tools, I'd say they
> should also patch the tools, though maybe a better idea would be to
> restrict the superuser a bit less.
>

They 'should', and I completely agree; but that isn't the reality today.
​Thus the patch.

Now it's understandable for the community to say 'not my problem' but
I'd say that depends on what it considers 'my problem'. If half the people
manage their installations on a cloud solution, it unwillingly becomes one.

Unrelated, it still does allow a non-superuser to take a dump sans the
password, which doesn't seem like a bad idea, since the patch
doesn't do anything more than dump from pg_roles, which is anyways
available to non-superusers.

I await if more object similarly.
-
robins

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2017-02-26 13:39:52 Re: Enabling parallelism for queries coming from SQL or other PL functions
Previous Message Robert Haas 2017-02-26 10:44:31 Re: Enabling parallelism for queries coming from SQL or other PL functions