Re: Refactor handling of database attributes between pg_dump and pg_dumpall
Haribabu Kommi <kommi.haribabu@gmail.com>
From: Haribabu Kommi <kommi.haribabu@gmail.com>
To: Thomas Munro <thomas.munro@enterprisedb.com>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>,
Andreas Karlsson <andreas@proxel.se>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2017-09-09T03:29:45Z
Lists: pgsql-hackers
Attachments
- 0001-pg_dump-and-pg_dumpall-database-handling-refactoring_v7.patch (application/octet-stream) patch v7-0001
On Fri, Sep 8, 2017 at 10:24 AM, Thomas Munro <thomas.munro@enterprisedb.com > wrote: > On Mon, Aug 21, 2017 at 4:35 PM, Haribabu Kommi > <kommi.haribabu@gmail.com> wrote: > > On Tue, Aug 15, 2017 at 7:29 AM, Peter Eisentraut > > <peter.eisentraut@2ndquadrant.com> wrote: > >> On 4/4/17 01:06, Haribabu Kommi wrote: > >> > Both pg_dump and pg_upgrade tests are passed. Updated patch attached > >> > I will add this patch to the next commitfest. > >> > >> This patch needs to be rebased for the upcoming commit fest. > > > > Thanks for checking. Rebased patch is attached. > > Hi Haribabu, > > This patch breaks the documentation build, possibly because of these empty > tags: > > + <option>--create</option> option to dump <>ALTER ROLE IN > DATABASE ... SET</> > Thanks for checking the patch. Fixed patch is attached. Regards, Hari Babu Fujitsu Australia
Commits
-
Move handling of database properties from pg_dumpall into pg_dump.
- b3f8401205af 11.0 landed
-
Allow pg_dumpall to dump roles w/o user passwords
- 9a83d56b38c8 10.0 cited
-
Fix pg_dumpall to work for databases flagged as read-only.
- 4bd371f6f886 9.4.0 cited