| From: | richard coleman <rcoleman(dot)ascentgl(at)gmail(dot)com> |
|---|---|
| To: | Tim <timfosho(at)gmail(dot)com> |
| Cc: | Erik Wienhold <ewie(at)ewie(dot)name>, pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pg_dump why no indicator of completion |
| Date: | 2023-05-02 12:28:24 |
| Message-ID: | CAGA3vBsSv+Dt=h2tGWUHFkqRT-RyC+h=yZz43t9nAhr6qyLBAA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Tim,
Thanks, but as I had previously mentioned, I had already taken care of that
little detail.
rik.
On Mon, May 1, 2023 at 11:22 PM Tim <timfosho(at)gmail(dot)com> wrote:
> > After reading the responses in this thread I've adjusted it to capture
> the exit status
>
> Just so I'm not a complete troll, heres your example which also appends a
> success/fail message :)
>
> nohup $(pg_dump ${connection_details} > something.log 2>&1 && echo "pgdump
> succeded" >> something.log || echo "pgdump failed" something.log) &
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sergey Cherevko | 2023-05-03 13:55:18 | unknown postgres ssl error "could not accept SSL connection: Success" and timeout |
| Previous Message | Ron | 2023-05-02 07:49:38 | Re: pg_dump why no indicator of completion |