Re: pg_dump why no indicator of completion

From: Ian Lawrence Barwick <barwick(at)gmail(dot)com>
To: richard coleman <rcoleman(dot)ascentgl(at)gmail(dot)com>
Cc: Scott Ribe <scott_ribe(at)elevated-dev(dot)com>, Ron <ronljohnsonjr(at)gmail(dot)com>, Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_dump why no indicator of completion
Date: 2023-05-02 03:14:45
Message-ID: CAB8KJ=iRfE-42b2skxNzz-_W9O=E2uae_nmm=Siyr+RBwTyKKg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

2023年5月1日(月) 22:26 richard coleman <rcoleman(dot)ascentgl(at)gmail(dot)com>:
>
> Scott,
>
> Generally I run pg_dump nohup in the background with all outputs captured to a file. Finding the exit message is simply a matter of navigating to the bottom of the output file and checking.
> Excepting for pg_dump, I don't generally have to worry about exit values as most command line programs are either short-lived and obvious, like ls, or emit their own text exit status.

If you do need to run pg_dump manually, have you considered running each
invocation in a terminal multiplexer such as "screen" or "tmux"? The
thought of long-running processes hanging around in NOHUP purgatory
fills me with a sense of impending doom.

Regards

Ian Barwick

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Tim 2023-05-02 03:21:58 Re: pg_dump why no indicator of completion
Previous Message Erik Wienhold 2023-05-02 03:05:39 Re: pg_dump why no indicator of completion