Re: pg_dump why no indicator of completion

From: Ron <ronljohnsonjr(at)gmail(dot)com>
To: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: pg_dump why no indicator of completion
Date: 2023-05-02 07:41:47
Message-ID: aed207be-9bc1-a4c7-99f7-25fc43703546@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Ron 2023-05-02 07:49:38 Re: pg_dump why no indicator of completion
Previous Message Tim 2023-05-02 03:21:58 Re: pg_dump why no indicator of completion