Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtp (Exim 4.84_2)
	(envelope-from
 <pgsql-hackers-owner+M318429=pgsql-hackers-arkari@postgresql.org>)
	id 1cgJIH-0008SF-KQ
	for pgsql-hackers@arkaria.postgresql.org; Tue, 21 Feb 2017 22:52:25 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
	by malur.postgresql.org with smtp (Exim 4.84_2)
	(envelope-from
 <pgsql-hackers-owner+M318429=pgsql-hackers-arkari@postgresql.org>)
	id 1cgJIH-00011O-7c
	for pgsql-hackers@arkaria.postgresql.org; Tue, 21 Feb 2017 22:52:25 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.84_2)
	(envelope-from <cloos@jhcloos.com>)
	id 1cgJIF-00010W-Si
	for pgsql-hackers@postgresql.org; Tue, 21 Feb 2017 22:52:23 +0000
Received: from ore.jhcloos.com ([198.147.22.87])
	by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.84_2)
	(envelope-from <cloos@jhcloos.com>)
	id 1cgJID-0001uu-2O
	for pgsql-hackers@postgresql.org; Tue, 21 Feb 2017 22:52:23 +0000
Received: by ore.jhcloos.com (Postfix, from userid 10)
	id 1BDB81E24C; Tue, 21 Feb 2017 22:52:15 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jhcloos.com;
	s=ore14; t=1487717536;
	bh=1AbCTrCXRXfZmE02JF7hAzs4JlrlCqi8bAZfy6aXnsA=;
	h=From:To:Cc:Subject:In-Reply-To:References:Date:From;
	b=MgeGugJjVcxogj5tI+Qtmd5ngK1Qm2/7eeqo58YKBPCW6Zqo5AH8vR/qgONGUHpe9
	 iwq0ZKxyOI/SGJ8P7gILU8Ui0FL9Gdj+byDpnE6aQ9S0+QFOylF+AK7CkydBaDhWBj
	 c5K2/EvzQXBWraeJY9Cd6n9KWE/LrGxz+GRfWhVM=
Received: by carbon.jhcloos.org (Postfix, from userid 500)
	id B5DA6107B7BE1; Tue, 21 Feb 2017 22:52:10 +0000 (UTC)
From: James Cloos <cloos@jhcloos.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andres Freund <andres@anarazel.de>,
  Petr Jelinek <petr.jelinek@2ndquadrant.com>,
  Robert Haas <robertmhaas@gmail.com>,
  "pgsql-hackers\@postgresql.org" <pgsql-hackers@postgresql.org>
Subject: Re: Replication vs. float timestamps is a disaster
In-Reply-To: <31590.1487599653@sss.pgh.pa.us> (Tom Lane's message of "Mon, 20
	Feb 2017 09:07:33 -0500")
References: <26788.1487455319@sss.pgh.pa.us>
	<CA+TgmoafyUzmg8T-rKEgmkX7F1iQLSrKBmqKa26EattXpMS-ng@mail.gmail.com>
	<1691.1487519369@sss.pgh.pa.us>
	<20170220070311.gscn7ppqbwlgdpjq@alap3.anarazel.de>
	<3bd3c551-8b23-45c8-27a2-97b5a922b130@2ndquadrant.com>
	<20170220110456.2jupmfhxlizykmmc@alap3.anarazel.de>
	<31590.1487599653@sss.pgh.pa.us>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux)
Face: iVBORw0KGgoAAAANSUhEUgAAABAAAAAQAgMAAABinRfyAAAACVBMVEX///8ZGXBQKKnCrDQ3
 AAAAJElEQVQImWNgQAAXzwQg4SKASgAlXIEEiwsSIYBEcLaAtMEAADJnB+kKcKioAAAAAElFTkSu
 QmCC
Copyright: Copyright 2016 James Cloos
OpenPGP: 0x997A9F17ED7DAEA6;
 url=https://jhcloos.com/public_key/0x997A9F17ED7DAEA6.asc
OpenPGP-Fingerprint: E9E9 F828 61A4 6EA9 0F2B  63E7 997A 9F17 ED7D AEA6
Date: Tue, 21 Feb 2017 17:52:10 -0500
Message-ID: <m337f7nomd.fsf@jhcloos.com>
Lines: 29
MIME-Version: 1.0
Content-Type: text/plain
X-Pg-Spam-Score: -2.0 (--)
List-Archive: <http://archives.postgresql.org/pgsql-hackers>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-hackers.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@postgresql.org>
List-Post: <mailto:pgsql-hackers@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-hackers>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
X-Mailing-List: pgsql-hackers
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

>>>>> "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 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@jhcloos.com>         OpenPGP: 0x997A9F17ED7DAEA6


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