| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Magne Mæhre <Magne(dot)Mahre(at)Sun(dot)COM> |
| Cc: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Trevor Talbot <quension(at)gmail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Aidan Van Dyk <aidan(at)highrise(dot)ca>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Timezone database changes |
| Date: | 2007-10-11 18:57:40 |
| Message-ID: | 4244.1192129060@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
=?ISO-8859-1?Q?Magne_M=E6hre?= <Magne(dot)Mahre(at)Sun(dot)COM> writes:
> Correct me if I'm wrong, but IIRC there is no universally accepted
> canonical list of time zone names (labels).
Yeah; we have an agreed-on list of names for the purposes of PG, namely
the names shown by pg_timezone_names, but that list changes from time to
time. What's worse, it might be different on some platforms than others
even for the same PG release, since some distros override our zic
database with the system's own.
So one of the problems that would have to be surmounted to have a
datatype that embeds a zone ID is to figure out a persistent, but
compact, ID to assign to each zone ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2007-10-11 18:58:45 | Re: Some questions about mammoth replication |
| Previous Message | andy | 2007-10-11 18:49:23 | Re: full text search in 8.3 |