Re: Allow pg_dumpall to work without pg_authid
Robins Tharakan <tharakan@gmail.com>
From: Robins Tharakan <tharakan@gmail.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2017-02-26T10:59:15Z
Lists: pgsql-hackers
On 26 February 2017 at 21:37, Robert Haas <robertmhaas@gmail.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
Commits
-
Fix dumping role comments when using --no-role-passwords
- d82cb467bbc2 12.19 landed
- be01c8c3450e 14.12 landed
- affc46b76d50 13.15 landed
- 7e65ad197f9d 17.0 landed
- 5863bacb87c1 16.3 landed
- 12128be623fd 15.7 landed