| From: | Rui DeSousa <rui(at)crazybean(dot)net> |
|---|---|
| To: | richard coleman <rcoleman(dot)ascentgl(at)gmail(dot)com> |
| Cc: | Frank Lanitz <frank(at)frank(dot)uvena(dot)de>, pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pg_dump why no indicator of completion |
| Date: | 2023-05-01 14:31:18 |
| Message-ID: | 8D0A91FC-C10C-4B68-9348-DA3F751FE470@crazybean.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
> On May 1, 2023, at 10:00 AM, richard coleman <rcoleman(dot)ascentgl(at)gmail(dot)com> wrote:
>
> As I've mentioned in another response I typically run pg_dump as follows:
>
> nohup pg_dump {various settings} > something.log 2>&1 &
Why redirect standard error to standard out when using pg_dump? I assume that using standard out is not the backup stream.
If you want a success message in the log; write the success message to the log file if pg_dump exits successfully.
i.e.: nohup pg_dump --verbose prod > prod.sql 2> prod.log && echo "Backup Completed Successfully!" >> prod.log &
| From | Date | Subject | |
|---|---|---|---|
| Next Message | richard coleman | 2023-05-01 14:34:16 | Re: pg_dump why no indicator of completion |
| Previous Message | richard coleman | 2023-05-01 14:31:11 | Re: pg_dump why no indicator of completion |