Date: Fri, 30 May 2025 12:09:48 +0200
From: hubert depesz lubaczewski <depesz@depesz.com>
Sender: depesz@depesz.com
To: Ron Johnson <ronljohnsonjr@gmail.com>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: pg_dump verbose start and stop times?
Message-ID: <aDmD7C-CTAesqkPl@depesz.com>
Reply-To: depesz@depesz.com
References: 
 <CANzqJaDPKWHUTnJMbwY2qqDk8YPSP=-b7dJbBGKbBLYnqkFjiQ@mail.gmail.com>
 <CAKFQuwb_V35L1VYAevfon9ZbHPUxFcwhY1Ei07MNSm_5_Z-QjA@mail.gmail.com>
 <CANzqJaBbTaQyNvAmuBU9oZTcKMUk+2JyNFpPnDELzKVFiQ5PfQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <CANzqJaBbTaQyNvAmuBU9oZTcKMUk+2JyNFpPnDELzKVFiQ5PfQ@mail.gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/aDmD7C-CTAesqkPl%40depesz.com>
Precedence: bulk

On Thu, May 29, 2025 at 08:51:49PM -0400, Ron Johnson wrote:
> The non-sense of putting start and stop times in the dump file while not
> putting them in stderr must have caused my brain to skip over "to the dump
> file".
> 
> Honestly, who cares if start and stop times are in the dump file?  stderr
> is where a DBA wants to see timings.

=$ date >&2; pg_dump …; date >&2

That's all you need.

Whether pg_dump does what you want, or not, is not really important
given how easy it is to fix the thing yourself.

And the assumption that: "it doesn't do what *I* want, so it's
non-sense", is slightly exaggerating commonality of your experience.

Best regards,

depesz