From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
---|---|
To: | Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
Cc: | Aftab Hussain <aftab(dot)se(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Patch for PKST timezone |
Date: | 2010-05-11 08:45:02 |
Message-ID: | 4BE9190E.40603@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Takahiro Itagaki wrote:
> Aftab Hussain <aftab(dot)se(at)gmail(dot)com> wrote:
>
>> Please accept attached patch for the following problem.
>
> This patch has not been replied, but I can reproduce the error with:
> =# SET timezone = 'Asia/Karachi';
> =# SELECT timeofday()::timestamptz;
> ERROR: invalid input syntax for type timestamp with time zone: "Tue May 11 13:26:53.264293 2010 PKST"
>
> Should we add PKST timezone? Also, I found a list of timezones[1]
> and we don't have 36 tznames in the list. Should we also need them?
I don't think we want to include all timezone names in the default
config, timezone abbreviations aren't always unique for example. But we
should include PKST because we already include PKT; it would be nasty
for an application to work during winter, and stop working when the
daylight saving time begins.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Mike Fowler | 2010-05-11 09:21:43 | Re: Adding xpath_exists function |
Previous Message | Takahiro Itagaki | 2010-05-11 08:03:30 | Re: Patch for PKST timezone |