From: | Isaac Morland <isaac(dot)morland(at)gmail(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, 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 00:07:08 |
Message-ID: | CAMsGm5fVOX+DCAQzx65+TBYj8wxutmG6Uc5U9BFZ=L+U_NpaZg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, 11 Apr 2020 at 19:36, Michael Paquier <michael(at)paquier(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Jose Luis Tallon | 2020-04-12 00:38:23 | Re: where should I stick that backup? |
Previous Message | Michael Paquier | 2020-04-11 23:36:25 | Re: pg_validatebackup -> pg_verifybackup? |