Horton

Re: pg_validatebackup -> pg_verifybackup?

Isaac Morland <isaac.morland@gmail.com>

View thread View on postgr.es
From: Isaac Morland <isaac.morland@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>, Robert Haas <robertmhaas@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, Andres Freund <andres@anarazel.de>, David Steele <david@pgmasters.net>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>, Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Date: 2020-04-12T00:07:08Z
Lists: pgsql-hackers 
On Sat, 11 Apr 2020 at 19:36, Michael Paquier <michael@paquier.xyz> wrote:


> Yeah, their stuff is nice.  Another nice thing is that git has the
> possibility to scan as well for custom scripts as long as they respect
> the naming convention, like having a custom script called "git-foo",
> that can be called as "git foo".
>

… which could be installed by an extension perhaps. Wait, that doesn't
quite work because it's usually one bin directory per version, not per
database. Still maybe something can be done with that idea.

Commits

  1. Rename pg_validatebackup to pg_verifybackup some more.

  2. Rename pg_validatebackup to pg_verifybackup.