From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
Cc: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_dump, pg_dumpall and data durability |
Date: | 2016-11-12 22:48:04 |
Message-ID: | CAB7nPqSPi90o310sSiv59YenwY1XtDw30A1TBfSCVk89DD=_Lw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, Nov 13, 2016 at 12:17 AM, Dilip Kumar <dilipbalaut(at)gmail(dot)com> wrote:
> On Sat, Nov 12, 2016 at 10:16 AM, Michael Paquier
> <michael(dot)paquier(at)gmail(dot)com> wrote:
>>> - For pg_dumpall, a short option "-N" is added for "--no-sync", but not for
>>> pg_dump (because -N is already taken there).
>>> I'd opt for either using the same short option for both or (IMO better)
>>> only offering a long option for both.
>>
>> Okay. For consistency's sake let's do that. I was a bit hesitant
>> regarding that to be honest.
>
> Seems like you have missed to remove -N at some places, as mentioned below.
>
> 1.
> --- a/doc/src/sgml/ref/pg_dumpall.sgml
> +++ b/doc/src/sgml/ref/pg_dumpall.sgml
> @@ -365,6 +365,21 @@ PostgreSQL documentation
> </varlistentry>
>
> <varlistentry>
> + <term><option>-N</option></term>
>
> @@ -543,6 +557,7 @@ help(void)
>
>
> 2.
> printf(_("\nGeneral options:\n"));
> printf(_(" -f, --file=FILENAME output file name\n"));
> + printf(_(" -N, --no-sync do not wait for changes to
> be written safely to disk\n"));
v4 fixed those two places.
> 3.
> - while ((c = getopt_long(argc, argv, "acd:f:gh:l:oOp:rsS:tU:vwWx",
> long_options, &optindex)) != -1)
> + while ((c = getopt_long(argc, argv, "acd:f:gh:l:NoOp:rsS:tU:vwWx",
> long_options, &optindex)) != -1)
But not this one...
--
Michael
Attachment | Content-Type | Size |
---|---|---|
pgdump-sync-v5.patch | application/x-patch | 12.9 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2016-11-13 03:00:35 | Re: pg_dump, pg_dumpall and data durability |
Previous Message | Tom Lane | 2016-11-12 21:20:19 | Re: More snapshot-management fun |