| From: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | "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-28 22:09:48 |
| Message-ID: | 1409263788.60223.YahooMailNeo@web122305.mail.ne1.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
> Kevin Grittner wrote:
>
>> But the standard doesn't say anything about storing a time zone
>> *name* or *abbreviation* -- it requires that it be stored as UTC
>> with the *offset* (in hours and minutes). That makes it pretty
>> close to what we have -- it's all about a difference in
>> presentation. And as far as I can see it completely dodges the
>> kinds of problems you're talking about.
>
> Yeah, it does, but is it useful?
More so than CHAR(n). It would have been beneficial to support for
the same reason.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2014-08-28 22:25:49 | Re: Why data of timestamptz does not store value of timezone passed to it? |
| Previous Message | Robert Haas | 2014-08-28 22:05:03 | Re: Function to know last log write timestamp |