From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: pg_dump why no indicator of completion
Date: Mon, 1 May 2023 11:15:02 -0500
Message-ID: <491f094b-93f9-6a7d-1846-901aa583171c@gmail.com> (raw)
In-Reply-To: <6EF026A5-5CEC-48AB-B27E-C225DAE6E10A@elevated-dev.com>
References: <CAGA3vBugp4Ce8ZbOfntb8HjCvo5QtX1hhAHj3iuCMZdzSTo4dg@mail.gmail.com>
<CAKFQuwaEckQ5T10RwLsAx5giGtz9B4RsJg=U6WbZBTGAPmKSBA@mail.gmail.com>
<6EF026A5-5CEC-48AB-B27E-C225DAE6E10A@elevated-dev.com>
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: pg_dump why no indicator of completion
In-Reply-To: <491f094b-93f9-6a7d-1846-901aa583171c@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox