Date: Fri, 30 May 2025 15:48:08 +0200
From: hubert depesz lubaczewski <depesz@depesz.com>
Sender: depesz@depesz.com
To: Ron Johnson <ronljohnsonjr@gmail.com>
Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: pg_dump verbose start and stop times?
Message-ID: <aDm3GG7Q3SPq3t21@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>
 <aDmD7C-CTAesqkPl@depesz.com>
 <CANzqJaDVuTUxG+=gWiP0+qPqgEaKXJNxnEj9vyLi+2G3KWROUQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <CANzqJaDVuTUxG+=gWiP0+qPqgEaKXJNxnEj9vyLi+2G3KWROUQ@mail.gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/aDm3GG7Q3SPq3t21%40depesz.com>
Precedence: bulk

On Fri, May 30, 2025 at 08:54:24AM -0400, Ron Johnson wrote:
> And yet it's not possible to show how long it takes to copy each object .
> This, at least, does the math to show the grand elapsed time, and puts an
> easily greppable string in the cron job's stdout+stderr log file:
> 
> time_it()
> {
>     local ActionLabel=$1
>     shift
>     date +"%n%F %T TIMEIT $ActionLabel started.%n"
>     START_SECS=$(date +"%s")
>     $@
>     local RC=$? ; echo "TIMEIT Return Code = $RC"
>     FINISH_SECS=$(date +"%s")
>     ET=$(echo "scale=2;(${FINISH_SECS} - ${START_SECS})/60" | bc)
>     date +"%n%F %T TIMEIT $ActionLabel finished. Elapsed time: ${ET}
> minutes."
>     return $RC
> }
> 
> time_it DUMP_$DB pg_dump -j ${Threads} -Z${ZLvl} -v -C -Fd --file=$DB $DB
> 2> ${DB}_pgdump.log

You do know that you could have just done:

time pg_dump …

without the time_it function?

And if you'd want to write your own function, assuming you're running
not-so-ancient bash, you could have just used $EPOCHREALTIME and not the
date +… ?

Best regards,

depesz