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

From Ron
Subject Re: pg_dump why no indicator of completion
Date
Msg-id 491f094b-93f9-6a7d-1846-901aa583171c@gmail.com
Whole thread Raw
In response to Re: pg_dump why no indicator of completion  (Scott Ribe <scott_ribe@elevated-dev.com>)
Responses Re: pg_dump why no indicator of completion
List pgsql-admin
On 5/1/23 10:50, Scott Ribe wrote:
On May 1, 2023, at 9:25 AM, David G. Johnston <david.g.johnston@gmail.com> wrote:

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.
It would be a reasonable convenience. I think some of the pushback is from the framing that not having it is a defect.

Exactly.  It's a convenience, the lack of which is easily worked around.

What would really be useful are timestamps (both start and completion of dump) and an easy association of ".dat numbers" with table names.

--
Born in Arizona, moved to Babylonia.

pgsql-admin by date:

Previous
From: M Sarwar
Date:
Subject: Re: pg_dump why no indicator of completion
Next
From: Tim
Date:
Subject: Re: pg_dump why no indicator of completion