Re: pg_dump why no indicator of completion - Mailing list pgsql-admin

From Ron
Subject Re: pg_dump why no indicator of completion
Date
Msg-id aed207be-9bc1-a4c7-99f7-25fc43703546@gmail.com
Whole thread Raw
In response to Re: pg_dump why no indicator of completion  (Tim <timfosho@gmail.com>)
List pgsql-admin
On 5/1/23 22:21, Tim 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) &

Out of curiosity, why this:
    > something.log 2>&1
instead of that?
    &> something.log

Yes, "&>" is a bashism, but so what?

--
Born in Arizona, moved to Babylonia.

pgsql-admin by date:

Previous
From: Tim
Date:
Subject: Re: pg_dump why no indicator of completion
Next
From: Ron
Date:
Subject: Re: pg_dump why no indicator of completion