From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: pg_dump - how to force to show timestamps in client log |
Date: | 2020-11-20 21:00:33 |
Message-ID: | 7919898d-f5c5-44f0-5af3-41808ba71dfc@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 11/20/20 2:56 PM, Adrian Klaver wrote:
> On 11/20/20 10:01 AM, Durumdara wrote:
>> Hello!
>>
>> We need to log the pg_dump's state.
>> What objects are in copy, and what are the starting and ending times.
>>
>> But when I try to redirect the output, the result doesn't have timestamps.
>>
>> PG 11, on Windows.
>>
>> As I see the -v option isn't enough to see the starting times.
>>
>> For example:
>>
>> 2020-11-19 12:00:01.084 Dump table content table1
>> 2020-11-19 12:03:12.932 Dump table content table2
>> ...
>> etc.
>
>
> If you are redirecting to a file it have the creation time that you can
> use. Internally times don't really matter for the objects as the dump is
> based on a snapshot. Said snapshot is based on visible transactions not
> time. So for practical purposes they all occur at the same 'time'.
It makes all the difference when monitoring the progress of a backup.
--
Angular momentum makes the world go 'round.
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2020-11-20 21:39:28 | Re: pg_dump - how to force to show timestamps in client log |
Previous Message | Adrian Klaver | 2020-11-20 20:56:35 | Re: pg_dump - how to force to show timestamps in client log |