public inbox for pgsql-docs@postgresql.org  

help / color / mirror / Atom feed

From: David G. Johnston <david.g.johnston@gmail.com>
To: camac2025@yahoo.com <camac2025@yahoo.com>
To: pgsql-docs@lists.postgresql.org <pgsql-docs@lists.postgresql.org>
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: <176593231445.978860.2300752490245961611@wrigleys.postgresql.org>
References: <176593231445.978860.2300752490245961611@wrigleys.postgresql.org>

On Tuesday, December 16, 2025, PG Doc comments form <noreply@postgresql.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.

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: pgsql-docs@postgresql.org
  Cc: david.g.johnston@gmail.com, camac2025@yahoo.com, pgsql-docs@lists.postgresql.org
  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