Re: commit time in logical decoding

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

Hello Artur,

Thank you for your reply.
Should it work in a stable version like Postgresql 9.4, since it's
enough for me and I don't care whether it's 9.6 or 9.5.
Nevertheless I will try it using 9.4.

Regards,
Weiping

On 01.03.2016 22:04, Artur Zakirov wrote:
> 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
>>
>>
>
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message David G. Johnston 2016-03-01 22:08:10 Re: multiple UNIQUE indices for FK
Previous Message Artur Zakirov 2016-03-01 21:04:36 Re: commit time in logical decoding