Horton

Re: pg_dump, pg_dumpall and data durability

Michael Paquier <michael.paquier@gmail.com>

View thread View on postgr.es
From: Michael Paquier <michael.paquier@gmail.com>
To: Albe Laurenz <laurenz.albe@wien.gv.at>
Cc: PostgreSQL mailing lists <pgsql-hackers@postgresql.org>
Date: 2017-01-23T04:02:12Z
Lists: pgsql-hackers

Attachments

On Tue, Nov 29, 2016 at 1:30 PM, Michael Paquier
<michael.paquier@gmail.com> wrote:
> On Mon, Nov 14, 2016 at 6:07 PM, Michael Paquier
> <michael.paquier@gmail.com> wrote:
>> On Mon, Nov 14, 2016 at 6:04 PM, Albe Laurenz <laurenz.albe@wien.gv.at> wrote:
>>> Michael Paquier wrote:
>>>> Meh. I forgot docs and --help output updates.
>>>
>>> Looks good, except that you left the "N" option in the getopt_long
>>> call for pg_dumpall.  I fixed that in the attached patch.
>>
>> No, v5 has removed it, but it does not matter much now...
>>
>>> I'll mark the patch "ready for committer".
>>
>> Thanks!
>
> Moved to CF 2017-01.

Moved to CF 2017-03 with the same status, ready for committer. Perhaps
there is some interest in this feature? v5 of the patch still applies,
with a couple of hunks, so v6 is attached.
-- 
Michael

Commits

  1. Sync pg_dump and pg_dumpall output