Re: pg_dump why no indicator of completion

From: Ron <ronljohnsonjr(at)gmail(dot)com>
To: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: pg_dump why no indicator of completion
Date: 2023-05-01 16:15:02
Message-ID: 491f094b-93f9-6a7d-1846-901aa583171c@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On 5/1/23 10:50, Scott Ribe wrote:
>> On May 1, 2023, at 9:25 AM, David G. Johnston<david(dot)g(dot)johnston(at)gmail(dot)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.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Tim 2023-05-02 01:29:50 Re: pg_dump why no indicator of completion
Previous Message M Sarwar 2023-05-01 15:51:54 Re: pg_dump why no indicator of completion