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

From Robert Haas
Subject Re: [HACKERS] Replication vs. float timestamps is a disaster
Date
Msg-id CA+TgmoafyUzmg8T-rKEgmkX7F1iQLSrKBmqKa26EattXpMS-ng@mail.gmail.com
Whole thread Raw
In response to [HACKERS] Replication vs. float timestamps is a disaster  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] Replication vs. float timestamps is a disaster  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sun, Feb 19, 2017 at 3:31 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Thoughts?  Should we double down on trying to make this work according
> to the "all integer timestamps" protocol specs, or cut our losses and
> change the specs?

I vote for doubling down.  It's bad enough that we have so many
internal details that depend on this setting; letting that cascade
into the wire protocol seems like it's just letting the chaos spread
farther and wider.

Also, I wonder if we could consider deprecating and removing
--disable-integer-datetimes at some point.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] Reporting xmin from VACUUMs
Next
From: Robert Haas
Date:
Subject: Re: [HACKERS] Partitioned tables and relfilenode