Re: [HACKERS] Replication vs. float timestamps is a disaster - Mailing list pgsql-hackers

From Petr Jelinek
Subject Re: [HACKERS] Replication vs. float timestamps is a disaster
Date
Msg-id 452dabb1-713b-ceef-7307-9315690935d6@2ndquadrant.com
Whole thread Raw
In response to Re: [HACKERS] Replication vs. float timestamps is a disaster  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On 20/02/17 12:04, Andres Freund wrote:
> On 2017-02-20 11:58:12 +0100, Petr Jelinek wrote:
>> That being said, I did wonder myself if we should just deprecate float
>> timestamps as well.
> 
> I think we need a proper deprecation period for that, given that the
> conversion away will be painful for pg_upgrade using people with big
> clusters.  So I think we should fix this regardless... :(
> 

That's a good point.

Attached should fix the logical replication problems. I am not quite
sure if there is anything in physical that needs changing.

I opted for GetCurrentIntegerTimestamp() in the reply code as that's the
same coding walreceiver uses.

-- 
  Petr Jelinek                  http://www.2ndQuadrant.com/
  PostgreSQL Development, 24x7 Support, Training & Services

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Attachment

pgsql-hackers by date:

Previous
From: Aleksander Alekseev
Date:
Subject: Re: [HACKERS] SCRAM authentication, take three
Next
From: Aleksander Alekseev
Date:
Subject: Re: [HACKERS] SCRAM authentication, take three