| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "hernan gonzalez" <hgonzalez(at)gmail(dot)com>, <pgsql-hackers(at)postgresql(dot)org>, "Andrew Gierth" <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
| Subject: | Re: Timezones (in 8.5?) |
| Date: | 2009-11-18 18:26:14 |
| Message-ID: | 4B03E7E6020000250002C9E9@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> wrote:
> If he meant (A), then you store the event as:
> (ts,tz) = (timestamp '2010-07-27 10:30:00',
> 'Chile/Santiago')
> If he meant (B), then you store the event as
> (tsz,tz) = (timestamp '2010-07-27 10:30:00' at time zone
> 'Chile/Santiago', 'Chile/Santiago')
You seem to be agreeing that these problems can't be solved without
storing a time zone string in addition to the timestamp. As I read
it, Hernán was wishing for types which include this, rather than
having to do the above dance with multiple values.
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Wojciech Knapik | 2009-11-18 19:13:10 | Re: Very bad FTS performance with the Polish config |
| Previous Message | Tom Lane | 2009-11-18 17:50:33 | Re: Python 3.1 support |