From: | David Fetter <david(at)fetter(dot)org> |
---|---|
To: | Robins Tharakan <tharakan(at)gmail(dot)com> |
Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, "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-22 15:59:03 |
Message-ID: | 20170222155903.GB18866@fetter.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Feb 22, 2017 at 06:33:10PM +1100, Robins Tharakan wrote:
> Stephen,
>
> On 20 February 2017 at 08:50, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
>
> > The other changes to use pg_roles instead of pg_authid when rolpassword
> > isn't being used look like they should just be changed to use pg_roles
> > instead of using one or the other. That should be an independent patch
> > from the one which adds the option we are discussing.
> >
>
> Sure. Attached are 2 patches, of which 1 patch just replaces
> pg_authid with pg_roles in pg_dumpall. The only exceptions
> there are buildShSecLabels() &
> pg_catalog.binary_upgrade_set_next_pg_authid_oid() which I thought
> should still use pg_authid.
Thanks for doing this!
That pg_dumpall didn't work with RDS Postgres (and possibly others)
was a pretty large wart.
In future, could you please leave patches uncompressed so they're
easier to see in the archives?
Best,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2017-02-22 16:31:19 | Re: pg_monitor role |
Previous Message | David Fetter | 2017-02-22 15:54:04 | Re: tablesample with partitioned tables |