| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, 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 14:19:07 |
| Message-ID: | CA+TgmoYNPMSq2wmw8wi1-oJ0ga4BuPMVPfZrhpEBT+FRpBbyew@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Apr 11, 2020 at 5:51 PM Alvaro Herrera <alvherre(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-04-12 14:25:40 | Re: Support for DATETIMEOFFSET |
| Previous Message | Magnus Hagander | 2020-04-12 14:09:13 | Re: where should I stick that backup? |