| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, 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 07:22:42 |
| Message-ID: | CBC19466-EDA3-4E10-9FC6-F293004D32EB@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 27 May 2019, at 03:52, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> pg_verify_checksums has been using -r for whatever reason, but as we
> do a renaming of the binary for v12 we could just fix that
> inconsistency as well.
The original patch used -o in pg_verify_checksums, the discussion of which
started in the below mail:
https://postgr.es/m/20180228194242.qbjasdtwm2yj5rqg%40alvherre.pgsql
Since -f was already used for “force check”, -r ended up being used. Now that
there no longer is a -f flag in pg_checksums, it can be renamed.
cheers ./daniel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Chochol | 2019-05-27 07:37:53 | Fix order of steps in DISCARD ALL documentation |
| Previous Message | Amit Langote | 2019-05-27 06:41:50 | Re: Excessive memory usage in multi-statement queries w/ partitioning |