Re: pg_dump, pg_dumpall and data durability

From: Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>
To: "'Michael Paquier *EXTERN*'" <michael(dot)paquier(at)gmail(dot)com>
Cc: PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_dump, pg_dumpall and data durability
Date: 2016-11-14 09:04:43
Message-ID: A737B7A37273E048B164557ADEF4A58B5397C5EF@ntex2010i.host.magwien.gv.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

I'll mark the patch "ready for committer".

Yours,
Laurenz Albe

Attachment Content-Type Size
pgdump-sync-v5.patch application/octet-stream 12.9 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2016-11-14 09:07:09 Re: pg_dump, pg_dumpall and data durability
Previous Message Michael Paquier 2016-11-14 08:52:04 Re: [PATCH] Allow TAP tests to be run individually