From: | richard coleman <rcoleman(dot)ascentgl(at)gmail(dot)com> |
---|---|
To: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
Cc: | Ron <ronljohnsonjr(at)gmail(dot)com>, Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: pg_dump why no indicator of completion |
Date: | 2023-05-01 13:01:34 |
Message-ID: | CAGA3vBu5oxwKvefhx+e2TgAK_ZFx2T-dk5b28bfj6n+YCW=3qA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Scott,
Which, running more than one command from the shell prompt in a single
logon session, or not emitting an exit message?
rik.
On Mon, May 1, 2023 at 8:59 AM Scott Ribe <scott_ribe(at)elevated-dev(dot)com>
wrote:
> > On May 1, 2023, at 6:56 AM, richard coleman <rcoleman(dot)ascentgl(at)gmail(dot)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...
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Ribe | 2023-05-01 13:07:06 | Re: pg_dump why no indicator of completion |
Previous Message | Scott Ribe | 2023-05-01 12:59:43 | Re: pg_dump why no indicator of completion |