From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: pg_dump why no indicator of completion
Date: Mon, 1 May 2023 08:43:05 -0500
Message-ID: <ac61c17e-1816-716e-9cb9-6d41682bc7c1@gmail.com> (raw)
In-Reply-To: <CAGA3vBsq49mS47iH9CpCjipxu-BP_85x9doEHrvP5jyaPuNN4Q@mail.gmail.com>
References: <CAGA3vBugp4Ce8ZbOfntb8HjCvo5QtX1hhAHj3iuCMZdzSTo4dg@mail.gmail.com>
<f68e9f75-4036-30c7-6d10-72dce6521bb3@gmail.com>
<CAGA3vBsq49mS47iH9CpCjipxu-BP_85x9doEHrvP5jyaPuNN4Q@mail.gmail.com>
On 5/1/23 07:56, richard coleman wrote:
> Ron,
> So what you are saying is that I have to write a shell script around
> pg_dump to catch the exit code of pg_dump since the developers of pg_dump
> didn't have pg_dump simply write an exit message?
>
> Since multiple pg_dump commands are often run at the same command prompt,
> and they can take hours, if not days to run,
Running a days-long pg_dump at any time except special occasions isn't very
wise. Especially from a command prompt.
Binary backup/restore programs are /much/ faster (if for no other reason
than they let you do incremental and differential backups).
> and there are a myriad of other commands the will be run in the interim,
> any exit code generated by pg_dump with be lost in the flotsam and jetsam
> of the multitude of exit codes created by every other command run between
> the calling of pg_dump and it's eventual termination. It could have
> completed successfully, crashed, been killed, etc.
>
> Or am I mistaken?
>
> thanks,
> rik.
>
> On Sun, Apr 30, 2023 at 11:28 PM Ron <ronljohnsonjr@gmail.com> wrote:
>
> 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.
>
--
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: <ac61c17e-1816-716e-9cb9-6d41682bc7c1@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