Re: pg_validatebackup -> pg_verifybackup? - Mailing list pgsql-hackers

From Robert Haas
Subject Re: pg_validatebackup -> pg_verifybackup?
Date
Msg-id CA+TgmoYNPMSq2wmw8wi1-oJ0ga4BuPMVPfZrhpEBT+FRpBbyew@mail.gmail.com
Whole thread Raw
In response to Re: pg_validatebackup -> pg_verifybackup?  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: pg_validatebackup -> pg_verifybackup?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sat, Apr 11, 2020 at 5:51 PM Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
> I like this idea so much that I already proposed it in the past[1], so +1.
>
> [1] https://postgr.es/m/20160826202911.GA320593@alvherre.pgsql

Hey, look at that. I think I had some vague recollection of a prior
proposal, but I couldn't remember exactly who or exactly what had been
proposed. I do think that pg_ctl is too long a prefix, though. People
can get used to typing 'pg createdb' instead of 'createdb' but 'pg_ctl
createdb' seems like too much. At least, it would very very quickly
cause me to install aliases.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: where should I stick that backup?
Next
From: Tom Lane
Date:
Subject: Re: Support for DATETIMEOFFSET