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

From David G. Johnston
Subject Re: pg_dump why no indicator of completion
Date
Msg-id CAKFQuwaEckQ5T10RwLsAx5giGtz9B4RsJg=U6WbZBTGAPmKSBA@mail.gmail.com
Whole thread Raw
In response to pg_dump why no indicator of completion  (richard coleman <rcoleman.ascentgl@gmail.com>)
Responses Re: pg_dump why no indicator of completion
List pgsql-admin
On Sun, Apr 30, 2023 at 5:18 PM richard coleman <rcoleman.ascentgl@gmail.com> wrote:
For example, I've been running a bunch of backups with pg_dump in directory mode with multiple jobs.  When I come back several hours later there are no pg_dump processes running.  The log is filled with:
dumping contents of foo
finished item 123456 of TABLE DATA bar


I agree that any log file that contains this level of detail regarding the operational detail can (IMO, should) also have an indication regarding the final outcome of the process.

The arguments about "the Unix way" seem to have forgotten the point about being silent except in cases of exception, and this level of detail already violates that premise.

David J.

pgsql-admin by date:

Previous
From: richard coleman
Date:
Subject: Re: pg_dump why no indicator of completion
Next
From: Rui DeSousa
Date:
Subject: Re: pg_dump why no indicator of completion