Re: pg_dump why no indicator of completion
| От | richard coleman |
|---|---|
| Тема | Re: pg_dump why no indicator of completion |
| Дата | |
| Msg-id | CAGA3vBu5oxwKvefhx+e2TgAK_ZFx2T-dk5b28bfj6n+YCW=3qA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: pg_dump why no indicator of completion (Scott Ribe <scott_ribe@elevated-dev.com>) |
| Ответы |
Re: pg_dump why no indicator of completion
|
| Список | 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@elevated-dev.com> wrote:
> 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...
В списке pgsql-admin по дате отправления: