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

From Robins Tharakan
Subject Re: [HACKERS] Allow pg_dumpall to work without pg_authid
Date
Msg-id CAEP4nAxodSit4mHRnsUcZNLqSF3g4DXSD4by5mmDaue52Qas_Q@mail.gmail.com
Whole thread Raw
In response to Re: [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
List pgsql-hackers

On 19 February 2017 at 17:02, Robins Tharakan <tharakan@gmail.com> wrote:
On Sun, 19 Feb 2017 at 10:08 Stephen Frost <sfrost@snowman.net> wrote:
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.


'--no-passwords' is a good alternative.
Would submit a patch soon.


After reviewing further, it seems that merely adding a password related workaround wouldn't suffice. Further --no-password is already an alias for -w, so that flag is effectively taken.

Since the main restriction with AWS RDS is the unavailability of pg_authid, probably that is a better basis to name the flag on.

Attaching a patch to add a new flag (--no-pgauthid) to pg_dumpall that can dump Globals without needing pg_authid. So the following works with AWS RDS Postgres databases.

pg_dumpall --no-pgauthid --globals-only > a.sql

I'll create a Commitfest entry, if there aren't many objections.

-
robins

Attachment

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] Parallel bitmap heap scan
Next
From: Robert Haas
Date:
Subject: Re: [HACKERS] Instability in select_parallel regression test