RE: pg_validatebackup -> pg_verifybackup?

Hi,

Sorry this email is not a discussion about word selection.
Since part of the manual had left pg_validatebackup in commit dbc60c5593f26dc777a3be032bff4fb4eab1ddd1.
I've attached a patch to fix this.

Regards,
Noriyoshi Shinoda

-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Monday, April 13, 2020 5:07 AM
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>; Magnus Hagander <magnus(at)hagander(dot)net>; Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>; David Steele <david(at)pgmasters(dot)net>; pgsql-hackers(at)postgresql(dot)org; Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Subject: Re: pg_validatebackup -> pg_verifybackup?

Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2020-04-12 11:21:50 -0400, Robert Haas wrote:
>> We could also have an alternate name, like pgsql, and make 'pg' a
>> symlink to it that packagers can choose to omit.

> We could even name the non-abbreviated binary postgres :).

I shudder to imagine the confusion that would result.

regards, tom lane