Quick Links

Re: Replication vs. float timestamps is a disaster

From:	Andres Freund <andres(at)anarazel(dot)de>
To:	Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com>
Cc:	Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-20 11:04:56
Message-ID:	20170220110456.2jupmfhxlizykmmc@alap3.anarazel.de
Views:	Raw Message \| Whole Thread \| Download mbox \| Resend email
Thread:
Lists:	pgsql-hackers

On 2017-02-20 11:58:12 +0100, Petr Jelinek wrote:
> That being said, I did wonder myself if we should just deprecate float
> timestamps as well.

I think we need a proper deprecation period for that, given that the
conversion away will be painful for pg_upgrade using people with big
clusters. So I think we should fix this regardless... :(

In response to

Re: Replication vs. float timestamps is a disaster at 2017-02-20 10:58:12 from Petr Jelinek

Responses

Re: Replication vs. float timestamps is a disaster at 2017-02-20 12:03:15 from Petr Jelinek
Re: Replication vs. float timestamps is a disaster at 2017-02-20 14:07:33 from Tom Lane
Re: Replication vs. float timestamps is a disaster at 2017-02-22 06:10:35 from Jim Nasby

Browse pgsql-hackers by date

	From	Date	Subject
Next Message	Dave Page	2017-02-20 11:21:58	pg_ls_waldir() & pg_ls_logdir()
Previous Message	Petr Jelinek	2017-02-20 10:58:12	Re: Replication vs. float timestamps is a disaster