From: Scott Ribe <scott_ribe@elevated-dev.com>
To: richard coleman <rcoleman.ascentgl@gmail.com>
Cc: Ron <ronljohnsonjr@gmail.com>
Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: pg_dump why no indicator of completion
Date: Mon, 1 May 2023 06:59:43 -0600
Message-ID: <B2494B4B-AE44-46AF-B4FC-D85374A145A7@elevated-dev.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 May 1, 2023, at 6:56 AM, richard coleman <rcoleman.ascentgl@gmail.com> wrote:
>
> Since multiple pg_dump commands are often run at the same command prompt, and they can take hours, if not days to run, 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.
That sounds like a really bad way to do things...
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: scott_ribe@elevated-dev.com, rcoleman.ascentgl@gmail.com, ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: pg_dump why no indicator of completion
In-Reply-To: <B2494B4B-AE44-46AF-B4FC-D85374A145A7@elevated-dev.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