| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> | 
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> | 
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> | 
| Subject: | Re: Why does pg_checksums -r not have a long option? | 
| Date: | 2019-05-27 14:22:37 | 
| Message-ID: | alpine.DEB.2.21.1905271616270.24257@lancre | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-hackers | 
Bonjour Michael,
> +     <varlistentry>
> +      <term><option>-f <replaceable>filenode</replaceable></option></term>
> +      <term><option>--filenode=<replaceable>filenode</replaceable></option></term>
> +      <listitem>
> +       <para>
> +        Only validate checksums in the relation with specified relation file node.
> +       </para>
> Two nits.  I would just have been careful about the number of
> characters in the line within the <para> markup.  And we use
> extensively "filenode" in the docs.
Ok.
> +       [ 'pg_checksums', '--enable', '-filenode', '1234', '-D', $pgdata ],
> This fails, but not for the reason it is written for.
Indeed. command_fails() is a little too simplistic, it should really check 
that the error message is there.
> It looks strange to not order --filenode alphabetically in --help.
Forgot, it stayed at the r position for no good reason.
> With all these issues cleaned up, I got the attached.  Does that look
> fine?  (I ran pgperltidy and pgindent on top of it.)
Works for me. Doc build is ok as well.
-- 
Fabien.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sascha Kuhl | 2019-05-27 14:34:48 | Re: Indexing - comparison of tree structures | 
| Previous Message | Antonin Houska | 2019-05-27 14:22:29 | Re: Converting NOT IN to anti-joins during planning |