| From: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
|---|---|
| To: | richard coleman <rcoleman(dot)ascentgl(at)gmail(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:07:06 |
| Message-ID: | 10EA4439-566E-412B-AF06-F4C04838C3A6@elevated-dev.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
> On May 1, 2023, at 7:01 AM, richard coleman <rcoleman(dot)ascentgl(at)gmail(dot)com> wrote:
>
> Which, running more than one command from the shell prompt in a single logon session, or not emitting an exit message?
Running multiple long-lived processes in a shell prompt, whose exit values you care about, running in the background, along with "a myriad of other commands", presumably short-lived, in the interim, then looking through "the flotsam and jetsam" for a success message. Sounds like a total mess. Put your important long-lived processesin their own sessions. Or, if you must interleave them, wrap the call to pg_dump in a simple conditional.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | richard coleman | 2023-05-01 13:26:28 | Re: pg_dump why no indicator of completion |
| Previous Message | richard coleman | 2023-05-01 13:01:34 | Re: pg_dump why no indicator of completion |