Re: pg_dump verbose start and stop times?

From: hubert depesz lubaczewski <depesz(at)depesz(dot)com>
To: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
Cc: pgsql-admin <pgsql-admin(at)postgresql(dot)org>
Subject: Re: pg_dump verbose start and stop times?
Date: 2025-05-30 10:09:48
Message-ID: aDmD7C-CTAesqkPl@depesz.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-admin

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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Andy Hartman 2025-05-30 10:29:54 Re: Seeking Suggestions for Best Practices: Archiving and Migrating Historical Data in PostgreSQL
Previous Message Motog Plus 2025-05-30 07:51:25 Seeking Suggestions for Best Practices: Archiving and Migrating Historical Data in PostgreSQL