From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: pg_dump why no indicator of completion |
Date: | 2023-05-01 13:37:42 |
Message-ID: | a785e088-c58f-b030-1c2e-91dea610bcae@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On 5/1/23 08:07, Scott Ribe wrote:
>> 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,
Exactly. Cron is your friend!!!
> 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.
--
Born in Arizona, moved to Babylonia.
From | Date | Subject | |
---|---|---|---|
Next Message | Ron | 2023-05-01 13:43:05 | Re: pg_dump why no indicator of completion |
Previous Message | richard coleman | 2023-05-01 13:26:28 | Re: pg_dump why no indicator of completion |