| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, "ktm(at)rice(dot)edu" <ktm(at)rice(dot)edu>, Bruce Momjian <bruce(at)momjian(dot)us>, Steve Crawford <scrawford(at)pinpointresearch(dot)com>, rohtodeveloper <rohtodeveloper(at)outlook(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Alexey <alexk(at)hintbits(dot)com> |
| Subject: | Re: Why data of timestamptz does not store value of timezone passed to it? |
| Date: | 2014-08-29 15:18:54 |
| Message-ID: | 19136.1409325534@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Kevin Grittner <kgrittn(at)ymail(dot)com> writes:
> It was actually rather disappointing to hear that we had a
> conforming implementation and changed away from it circa the 7.2
> release;
That is not the case. The existing implementation is work that Tom
Lockhart did around 6.3 or so. It was called timestamp at the time,
and was renamed to timestamp with time zone in 7.2, in order to make
room for timestamp without time zone (which I think *is* spec compliant
or close enough). That was probably an unfortunate choice; but at
no time was there code in PG that did what the spec says timestamp
with time zone should do.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G Johnston | 2014-08-29 15:19:09 | Re: Why data of timestamptz does not store value of timezone passed to it? |
| Previous Message | Michael Paquier | 2014-08-29 15:17:08 | Re: Misleading error message in logical decoding for binary plugins |