From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: pg_dump why no indicator of completion
Date: Sun, 30 Apr 2023 22:28:27 -0500
Message-ID: <f68e9f75-4036-30c7-6d10-72dce6521bb3@gmail.com> (raw)
In-Reply-To: <CAGA3vBugp4Ce8ZbOfntb8HjCvo5QtX1hhAHj3iuCMZdzSTo4dg@mail.gmail.com>
References: <CAGA3vBugp4Ce8ZbOfntb8HjCvo5QtX1hhAHj3iuCMZdzSTo4dg@mail.gmail.com>
On 4/30/23 19:18, richard coleman wrote:
> Hi all,
>
> I've been working with pg_dump and one thing that's always struck me as
> strange is that there never seems to be an indication in the log that the
> pg_dump process completed successfully.
>
> For example, I've been running a bunch of backups with pg_dump in
> directory mode with multiple jobs. When I come back several hours later
> there are no pg_dump processes running. The log is filled with:
>
> dumping contents of foo
> finished item 123456 of TABLE DATA bar
> etc.
>
>
> Other than trying to restore the multi terabyte database somewhere else is
> there any way to know that it actually finished successfully?
>
> Why doesn't pg_dump add a line in the output like:
>
> pg_backup finished
>
> when it's completed successfully?
>
> This seems like a terrible oversight.
>
> Am I missing something obvious?
"They" expect you to do the Unix Thing and check $?. Thus, that's what I do;
any non-zero value generates an email with a scary subject line, the
specifics of which are based on the exact code value. I'm not near my work
computer; otherwise I'd share them with you.
--
Born in Arizona, moved to Babylonia.
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-admin@postgresql.org
Cc: ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: pg_dump why no indicator of completion
In-Reply-To: <f68e9f75-4036-30c7-6d10-72dce6521bb3@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 DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox