pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
Cc: Jim Nasby <Jim.Nasby@BlueTreble.com>
Cc: Andres Freund <andres@anarazel.de>
Cc: Petr Jelinek <petr.jelinek@2ndquadrant.com>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Subject: Re: Replication vs. float timestamps is a disaster
Date: Wed, 22 Feb 2017 10:45:00 -0500
Message-ID: <919.1487778300@sss.pgh.pa.us> (raw)
In-Reply-To: <f733bd4c-fd12-29c1-83c0-1c8073bd970b@2ndQuadrant.com>
References: <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>
	<fece0003-6ede-ca8b-8f26-3c6fa899583d@BlueTreble.com>
	<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>
	<f733bd4c-fd12-29c1-83c0-1c8073bd970b@2ndQuadrant.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

Andrew Dunstan <andrew.dunstan@2ndquadrant.com> 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



view thread (33+ messages)  latest in thread

Message-ID: <919.1487778300@sss.pgh.pa.us>
Permalink:  ../919.1487778300@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/919.1487778300@sss.pgh.pa.us

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: tgl@sss.pgh.pa.us, andrew.dunstan@2ndquadrant.com, Jim.Nasby@BlueTreble.com, andres@anarazel.de, petr.jelinek@2ndquadrant.com, robertmhaas@gmail.com
  Subject: Re: Replication vs. float timestamps is a disaster
  In-Reply-To: <919.1487778300@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox