| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Thomas Lockhart <lockhart(at)fourpalms(dot)org> |
| Cc: | Thomas Lockhart <thomas(at)fourpalms(dot)org>, PostgreSQL Hackers List <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: More time zones |
| Date: | 2002-02-26 01:59:37 |
| Message-ID: | 200202260159.g1Q1xbg26197@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Thomas Lockhart wrote:
> > This is related to the Australian timezone duplication where we have a
> > GUC parameter. Could we generalize the GUC stuff to allow arbitrary
> > timezone mappings? Just an idea. Not sure it is worth it. The
> > Australians complained but I have not hear complaints from other
> > countries.
>
> I don't recall that "the Australians complained". Did their consulate
> call you? ;)
>
> What was the issue? Was the previous compile-time behavior preferable to
> some?
No, the Australians complained about the compile-time flag, and were
very happy when it became a GUC parameter. I only mentioned to say that
conflicting timezone issues are obviously a problem for some, and we did
resolve it with GUC.
> In any case, we do have to understand how to support areas which have
> conflicting definitions for character time zones, so if there are
> problems we need to be specific or be satisfied with the result.
Yes, Australia is the only group to have complained, and I think they
are happy with GUC.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Lockhart | 2002-02-26 02:18:40 | Re: More time zones |
| Previous Message | Thomas Lockhart | 2002-02-26 01:35:48 | Re: More time zones |