| From: | James Cloos <cloos(at)jhcloos(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers\(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Replication vs. float timestamps is a disaster |
| Date: | 2017-02-21 22:52:10 |
| Message-ID: | m337f7nomd.fsf@jhcloos.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>>>>> "TL" == Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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 for timestamp 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(at)jhcloos(dot)com> OpenPGP: 0x997A9F17ED7DAEA6
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-02-21 22:59:08 | Re: safer node casting |
| Previous Message | Jeff Janes | 2017-02-21 22:49:57 | Re: safer node casting |