| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_checksums --help synopsis is quite long |
| Date: | 2019-08-23 06:49:12 |
| Message-ID: | alpine.DEB.2.21.1908230842060.8996@lancre |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello Peter,
> With the additional functionality, the --help synopsis of pg_checksums
> has gotten quite long:
>
> pg_checksums enables, disables, or verifies data checksums in a
> PostgreSQL database cluster.
>
> Can we try to shorten this a bit? Maybe
>
> pg_checksums manages data checksums in a PostgreSQL database cluster.
>
> Other ideas?
My 0.02 €:
pg_checksums triggers or verifies checksums in a Postgres cluster.
I like the somehow detailed functionality list, if space allows, so I
tried to compressed the other parts.
Not sure that there could be a checksum on anything else but data.
I have decided that PostgreSQL is a mouthful, thus I'm rather using
"Postgres".
--
Fabien.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2019-08-23 07:59:25 | Re: pg_checksums --help synopsis is quite long |
| Previous Message | Masahiko Sawada | 2019-08-23 06:35:01 | Re: [HACKERS] [PATCH] pageinspect function to decode infomasks |