From: | chris(dot)bitmead(at)health(dot)gov(dot)au |
---|---|
To: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PATCHES] Australian timezone configure option |
Date: | 2001-06-14 01:21:46 |
Message-ID: | CA256A6B.00081157.00@mtascbr01.notes.health.gov.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>I will point out that "you Australians", and, well, "us 'mericans", are
>the only countries without the sense to choose unique conventions for
>time zone names.
I once had a long discussion about that on the timezone mailing lists.
If I remember right I think the upshot is that these are not the only
conflicts, they're probably just the only conflicts you have run across.
>It sounds like having a second lookup table for the Australian rules is
>a possibility, and this sounds fairly reasonable to me. Btw, is there an
>Australian convention for referring to North American time zones for
>those zones with naming conflicts?
Well aren't there long names for all the zones like Australia/NSW,
Australia/QLD, Australia/VIC etc?
I have at times heard people refer to AEST meaning Australian Eastern standard
time. I agree it's a big
mess but I couldn't even convince the timezone people there was even a problem.
Oh well.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-06-14 01:27:20 | Re: Re: [PATCHES] Fw: Isn't pg_statistic a security hole - Solution Proposal |
Previous Message | Tom Lane | 2001-06-14 01:20:30 | Re: Australian timezone configure option |