Confusing with commit time usage in logical decoding - Mailing list pgsql-general

From Weiping Qu
Subject Confusing with commit time usage in logical decoding
Date
Msg-id 56D4197E.9050706@informatik.uni-kl.de
Whole thread Raw
Responses Re: Confusing with commit time usage in logical decoding  (Andres Freund <andres@anarazel.de>)
List pgsql-general
If you received this message twice, sorry for annoying since I did not
subscribe successfully previously due to conflicting email domain.

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


pgsql-general by date:

Previous
From: Albe Laurenz
Date:
Subject: Re: Only owners can ANALYZE tables...seems overly restrictive
Next
From: Rafal Pietrak
Date:
Subject: Re: multiple UNIQUE indices for FK