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

From Ian Lawrence Barwick
Subject Re: pg_dump why no indicator of completion
Date
Msg-id CAB8KJ=iRfE-42b2skxNzz-_W9O=E2uae_nmm=Siyr+RBwTyKKg@mail.gmail.com
Whole thread Raw
In response to Re: pg_dump why no indicator of completion  (richard coleman <rcoleman.ascentgl@gmail.com>)
List pgsql-admin
2023年5月1日(月) 22:26 richard coleman <rcoleman.ascentgl@gmail.com>:
>
> Scott,
>
> Generally I run pg_dump nohup in the background with all outputs captured to a file.  Finding the exit message is
simplya 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-livedand 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



pgsql-admin by date:

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