Re: pg_dump why no indicator of completion - Mailing list pgsql-admin

From Scott Ribe
Subject Re: pg_dump why no indicator of completion
Date
Msg-id B2494B4B-AE44-46AF-B4FC-D85374A145A7@elevated-dev.com
Whole thread Raw
In response to Re: pg_dump why no indicator of completion  (richard coleman <rcoleman.ascentgl@gmail.com>)
Responses Re: pg_dump why no indicator of completion
List pgsql-admin
> 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
lostin the flotsam and jetsam of the multitude of exit codes created by every other command run between the calling of
pg_dumpand it's eventual termination. It could have completed successfully, crashed, been killed, etc. 

That sounds like a really bad way to do things...


pgsql-admin by date:

Previous
From: richard coleman
Date:
Subject: Re: pg_dump why no indicator of completion
Next
From: richard coleman
Date:
Subject: Re: pg_dump why no indicator of completion