public inbox for [email protected]
help / color / mirror / Atom feedFrom: David G. Johnston <[email protected]>
To: [email protected] <[email protected]>
To: [email protected] <[email protected]>
Subject: Re: missing documentation detail?
Date: Wed, 17 Dec 2025 06:20:07 -0700
Message-ID: <CAKFQuwY_LkJSx8j-TzK3+kuTRDr6OH6oVim-V7e0+f7zfDLDrA@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
On Tuesday, December 16, 2025, PG Doc comments form <[email protected]>
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.
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: missing documentation detail?
In-Reply-To: <CAKFQuwY_LkJSx8j-TzK3+kuTRDr6OH6oVim-V7e0+f7zfDLDrA@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox