Re: pg_validatebackup -> pg_verifybackup?

From: Andres Freund <andres(at)anarazel(dot)de>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, David Steele <david(at)pgmasters(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Subject: Re: pg_validatebackup -> pg_verifybackup?
Date: 2020-04-12 19:39:12
Message-ID: 20200412193912.2dty2r66wvc57ahm@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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 :).

Sure, that'd cause a bit more trouble upgrading for people that scripted
starting postgres without going through pg_ctl or such, but OTOH it'd
not cause new naming conflicts. And all that'd be needed to fix the
start script would be 's/postgres/postgres server/'.

- Andres

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2020-04-12 20:07:15 Re: pg_validatebackup -> pg_verifybackup?
Previous Message Andres Freund 2020-04-12 19:32:51 Re: pg_validatebackup -> pg_verifybackup?