| From: | Weiping Qu <qu(at)informatik(dot)uni-kl(dot)de> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Confusing with commit time usage in logical decoding |
| Date: | 2016-02-29 10:01:30 |
| Message-ID: | 56D416FA.2090108@informatik.uni-kl.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Weiping Qu | 2016-02-29 10:12:14 | Confusing with commit time usage in logical decoding |
| Previous Message | Albe Laurenz | 2016-02-29 09:52:33 | Re: Only owners can ANALYZE tables...seems overly restrictive |