Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cgZ6m-0001L2-T2 for pgsql-hackers@arkaria.postgresql.org; Wed, 22 Feb 2017 15:45:36 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cgZ6m-0002ti-G2 for pgsql-hackers@arkaria.postgresql.org; Wed, 22 Feb 2017 15:45:36 +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 ) id 1cgZ6l-0002t4-AO for pgsql-hackers@postgresql.org; Wed, 22 Feb 2017 15:45:35 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cgZ6L-0000VN-S2 for pgsql-hackers@postgresql.org; Wed, 22 Feb 2017 15:45:34 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id v1MFj0YN000920; Wed, 22 Feb 2017 10:45:00 -0500 From: Tom Lane To: Andrew Dunstan cc: Jim Nasby , Andres Freund , Petr Jelinek , Robert Haas , "pgsql-hackers@postgresql.org" Subject: Re: Replication vs. float timestamps is a disaster In-reply-to: References: <1691.1487519369@sss.pgh.pa.us> <20170220070311.gscn7ppqbwlgdpjq@alap3.anarazel.de> <3bd3c551-8b23-45c8-27a2-97b5a922b130@2ndquadrant.com> <20170220110456.2jupmfhxlizykmmc@alap3.anarazel.de> <20170222075345.mbzrmdaetdqfgitk@alap3.anarazel.de> <21041.1487771008@sss.pgh.pa.us> <20170222135634.gnlqu6by2xbpvwii@alap3.anarazel.de> <49985f09-7498-9a84-008b-638cbaebb044@BlueTreble.com> <20170222151230.zy7q7qmfah22lcxt@alap3.anarazel.de> <8ac3b446-00e0-2813-e67a-0498fac0f9b0@BlueTreble.com> Comments: In-reply-to Andrew Dunstan message dated "Wed, 22 Feb 2017 10:27:00 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <918.1487778300.1@sss.pgh.pa.us> Date: Wed, 22 Feb 2017 10:45:00 -0500 Message-ID: <919.1487778300@sss.pgh.pa.us> X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org Andrew Dunstan writes: > On 02/22/2017 10:21 AM, Jim Nasby wrote: >> Only in the catalog though, not the datums, right? I would think you >> could just change the oid in the catalog the same as you would for a >> table column. > No, in the datums. Yeah, I don't see any way that we could fob off float timestamps to an extension that would be completely transparent at the pg_upgrade level. And even a partial solution would be an enormous amount of fundamentally dead-end work. There has never been any project policy that promises everybody will be able to pg_upgrade until the end of time. I think it's not unreasonable for us to say that anyone still using float timestamps has to go through a dump and reload to get to v10. The original discussion about getting rid of them was ten years ago come May; that seems long enough. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers