Re: commit time in logical decoding
От | Artur Zakirov |
---|---|
Тема | Re: commit time in logical decoding |
Дата | |
Msg-id | 56D603E4.7040008@postgrespro.ru обсуждение исходный текст |
Ответ на | commit time in logical decoding (Weiping Qu <qu@informatik.uni-kl.de>) |
Ответы |
Re: commit time in logical decoding
|
Список | 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
В списке pgsql-general по дате отправления: