From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
Cc: | Shahbaz Javeed <sjaveed(at)gmail(dot)com>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: AT TIME ZONE |
Date: | 2004-08-24 19:46:17 |
Message-ID: | 6897.1093376777@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> writes:
> I wonder instead if it will be possible to store a timestamp without
> timezone in one field, and a timezone in another field. So I can get
> back a timestamp at the second-field timezone.
"f1 AT TIME ZONE f2" would be exactly the way to do that.
> I know this works for abbreviations, but this doesn't help me solve the
> problem at DST boundaries (abbreviations change at that point).
Right, what we are talking about here is extending AT TIME ZONE to
accept full zic-database zone names.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-08-24 19:49:56 | Re: server crash in very big transaction [postgresql 8.0beta1] |
Previous Message | Alvaro Herrera | 2004-08-24 19:35:52 | Re: AT TIME ZONE |