[SUGGESTION] Add duration of pg_dump operation to log file entries

[melmatsuoka]

Since the backup operation this script is effectively “silent” to the user (esp. if the script is run as a background process, cron job, or LaunchAgent on macOS), I find it informative to know how long it took the pg_dump process to complete each backup operation. Particularly since Resolve databases can get ridiculously large if you aren't diligent about housekeeping.

So instead of a log entry that looks like this:

Created Resolve_m9_server_PostgresDump_2017-08-13_200006.sqlc

The entry would look like this:

Created Resolve_m9_server_PostgresDump_2017-08-13_201811.sqlc in 121 seconds

I've implemented this in my fork, and can submit a pull request.

[IgorRidanovic]

Go ahead submit a pull request if you would.