| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "camac2025(at)yahoo(dot)com" <camac2025(at)yahoo(dot)com>, "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: missing documentation detail? |
| Date: | 2025-12-17 13:20:07 |
| Message-ID: | CAKFQuwY_LkJSx8j-TzK3+kuTRDr6OH6oVim-V7e0+f7zfDLDrA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Tuesday, December 16, 2025, PG Doc comments form <noreply(at)postgresql(dot)org>
wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/18/app-pgverifybackup.html
> Description:
>
> I was disappointed not to find the return code information on the
> pg_verifybackup pages - I am using the utility in a script and it seems I
> cannot distinguish between an invalid or 'bad' backup and a failed run (due
> to e.g. bad path, missing manifest file) - it *seems* that either will
> simply return as 1 but I am not certain. I would like to differentiate
> between these states.
>
This isn’t a good place to request feature enhancements. There isn’t an
issue with the documentation - the program doesn’t provide multiple
conditional exit codes.
Post a patch to -hackers or a feature request to -general (mailing list).
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2025-12-17 13:33:02 | Re: md5 reference |
| Previous Message | Mikael Gustavsson | 2025-12-17 13:16:27 | SV: md5 reference |