Re: commit time in logical decoding

From: Artur Zakirov <a(dot)zakirov(at)postgrespro(dot)ru>
To: Weiping Qu <qu(at)informatik(dot)uni-kl(dot)de>, pgsql-general(at)postgresql(dot)org
Subject: Re: commit time in logical decoding
Date: 2016-03-01 21:04:36
Message-ID: 56D603E4.7040008@postgrespro.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hello, Weiping

It seems that it is a bug. Thank you for report. I guess it will be
fixed soon.

On 01.03.2016 17:36, Weiping Qu wrote:
> Dear postgresql general mailing list,
>
> I am currently using the logical decoding feature (version 9.6 I think
> as far as I found in the source, wal_level: logical,
> max_replication_slot: > 1, track_commit_timestamp: on, I am not sure
> whether this will help or not).
> Following the online documentation, everything works fine until I input
>
> SELECT * FROM pg_logical_slot_peek_changes('regression_slot', NULL,
> NULL, 'include-timestamp', 'on');
>
>
> I always got 1999-12-31 16:00 as the commit time for arbitrary
> transactions with DML statements.
> After several tries, I realize that the txn->commit_time returned was
> always 0.
> Could you help me by indicating me what could be wrong in my case? Any
> missing parameters set?
>
> Thank you in advance,
> Kind Regards,
> Weiping
>
>

--
Artur Zakirov
Postgres Professional: http://www.postgrespro.com
Russian Postgres Company

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Weiping Qu 2016-03-01 21:16:24 Re: commit time in logical decoding
Previous Message Steven Xu 2016-03-01 20:54:15 Custom column ordering