| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, 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 15:06:25 |
| Message-ID: | 6937.1273590385@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
> Takahiro Itagaki wrote:
>> 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.
I don't think that's actually it. It looks to me like the Asia/Karachi
zone definition expects the abbreviations to be PKST and PKDT. Not sure
whether PKT is really in use, but it is not sensible to add PKST by
itself.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-05-11 16:08:04 | Re: PATCH: Minor notes in CLUSTER page |
| Previous Message | Robert Haas | 2010-05-11 15:04:29 | Re: SHARE locks vs. DELETE in SERIALIZABLE mode (Was: Partitioning/inherited tables vs FKs) |