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

From James Cloos
Subject Re: [HACKERS] Replication vs. float timestamps is a disaster
Date
Msg-id m337f7nomd.fsf@jhcloos.com
Whole thread Raw
In response to Re: [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  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-hackers
>>>>> "TL" == Tom Lane <tgl@sss.pgh.pa.us> writes:

TL> The question to be asked is whether there is still anybody out there
TL> using float timestamps.

Gentoo's ebuild includes:
  $(use_enable !pg_legacytimestamp integer-datetimes) \

meaning that by default --enable-integer-datetimes is passed to configure,
but if the pg_legacytimestamp use flag is set, then --disable-integer-datetimes
is passed instead.

They document it as:
   <flag name="pg_legacytimestamp">       Use double precision floating-point numbers instead of 64-bit       integers
fortimestamp storage.   </flag>
 

Ie, w/o any kind of deprecation notice.

I don't know how many (how few?) add pg_legacytimestamp to USE when
merging postgresql.  But it is still available as of 9.6 and also
with their live build of git://git.postgresql.org/git/postgresql.git.

-JimC
-- 
James Cloos <cloos@jhcloos.com>         OpenPGP: 0x997A9F17ED7DAEA6



pgsql-hackers by date:

Previous
From: Jeff Janes
Date:
Subject: Re: [HACKERS] safer node casting
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] safer node casting