public inbox for [email protected]
help / color / mirror / Atom feedFrom: Ron Johnson <[email protected]>
To: Pgsql-admin <[email protected]>
Subject: Re: pg_dump verbose start and stop times?
Date: Fri, 30 May 2025 11:02:23 -0400
Message-ID: <CANzqJaD6z-mavVkiYM4SPmKuPTva6JSE4S0zgqsMcVVJYxDNYQ@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CANzqJaDPKWHUTnJMbwY2qqDk8YPSP=-b7dJbBGKbBLYnqkFjiQ@mail.gmail.com>
<CAKFQuwb_V35L1VYAevfon9ZbHPUxFcwhY1Ei07MNSm_5_Z-QjA@mail.gmail.com>
<CANzqJaBbTaQyNvAmuBU9oZTcKMUk+2JyNFpPnDELzKVFiQ5PfQ@mail.gmail.com>
<[email protected]>
<CANzqJaDVuTUxG+=gWiP0+qPqgEaKXJNxnEj9vyLi+2G3KWROUQ@mail.gmail.com>
<[email protected]>
On Fri, May 30, 2025 at 9:48 AM hubert depesz lubaczewski <[email protected]>
wrote:
> 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?
>
Without the easily greppable string that shows what action it performed.
That's why I wrote the function: to have a standard, constant string to
grep.
> 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 +… ?
>
RHEL 8 is apparently ancient.
When all my RHEL 7 and 8 servers are retired, I might change it to use
$EPOCHREALTIME. Or maybe not; ancient, forgotten servers lurk everywhere,
and this probably works on RHEL 6.
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
reply
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: [email protected]
Cc: [email protected], [email protected]
Subject: Re: pg_dump verbose start and stop times?
In-Reply-To: <CANzqJaD6z-mavVkiYM4SPmKuPTva6JSE4S0zgqsMcVVJYxDNYQ@mail.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 agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox