From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Tomáš Vondra <tv(at)fuzzy(dot)cz> |
Subject: | Re: Fwd: patch: make_timestamp function |
Date: | 2014-02-19 21:15:21 |
Message-ID: | 15019.1392844521@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> My conclusion here is that the "time with time zone" datatype is broken
> in itself, because of this kind of ambiguity.
That's the conclusion that's been arrived at by pretty much everybody
who's looked at it with any care.
> Maybe we should just
> avoid offering more functionality on top of it, that is get rid of
> make_timetz() in this patch?
+1. We don't need to encourage people to use that type.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Neil Thombre | 2014-02-19 21:15:31 | pg_standby: Question about truncation of trigger file in fast failover |
Previous Message | Pavel Stehule | 2014-02-19 20:31:18 | Re: Fwd: patch: make_timestamp function |