Re: the include-timestamp data returned by pg_logical_slot_peek_changes() is always 2000-01-01 in 9.5.1

From: Andres Freund <andres(at)anarazel(dot)de>
To: Craig Ringer <craig(at)2ndquadrant(dot)com>, 李海龙 <hailong(dot)li(at)qunar(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: the include-timestamp data returned by pg_logical_slot_peek_changes() is always 2000-01-01 in 9.5.1
Date: 2016-03-09 15:31:32
Message-ID: 92E57CB4-CC68-4471-A459-FD96FF78139D@anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On March 9, 2016 4:26:01 AM PST, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:
>On 9 March 2016 at 18:13, 李海龙 <hailong(dot)li(at)qunar(dot)com> wrote:
>
>>
>>
>> HI, pgsql-hackers
>>
>> The include-timestamp data returned by
>pg_logical_slot_peek_changes() is
>> always 2000-01-01 in 9.5.1, is it not normal？

It's a bug in 9.5, that has been fixed. You can either update to the version from git, wait for the next minor release, or use 9.4, where the buff is not present.

>Did you enable track_commit_timestamps in the server?

That's unrelated, commit ts is about an xid timestamp mapping.

Andres
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Christian Ullrich 2016-03-09 15:36:06 Re: Crash with old Windows on new CPU
Previous Message Alvaro Herrera 2016-03-09 15:12:34 Re: OOM in libpq and infinite loop with getCopyStart()