| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>, 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-28 01:00:23 |
| Message-ID: | 8f819ff5-0162-f382-72d1-da565ceb4125@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 02/22/2017 02:45 PM, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
>> On 2017-02-22 08:43:28 -0500, Tom Lane wrote:
>>> (To be concrete, I'm suggesting dropping --disable-integer-datetimes
>>> in HEAD, and just agreeing that in the back branches, use of replication
>>> protocol with float-timestamp servers is not supported and we're not
>>> going to bother looking for related bugs there. Given the lack of field
>>> complaints, I do not believe anyone cares.)
>
> What I *am* willing to spend time on is removing float-timestamp code
> in HEAD. I've not yet heard anybody speak against doing that (or at
> least, nothing I interpreted as a vote against it). If I've not heard
> any complaints by tomorrow, I'll get started on that.
Rip it out!
Sincerely,
JD
--
Command Prompt, Inc. http://the.postgres.company/
+1-503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Everyone appreciates your honesty, until you are honest with them.
Unless otherwise stated, opinions are my own.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2017-02-28 01:13:32 | Re: Replication vs. float timestamps is a disaster |
| Previous Message | Bruce Momjian | 2017-02-28 00:53:56 | Re: Replication vs. float timestamps is a disaster |