Bruce Momjian wrote:
> Woh, I am sorry to jump in here, but we have to go by whatever Unix
> gives us as a timezone. If Unix can't get it right, I don't think
> postgreSQL should be messing with it.
>
> Or am I missing something here. Are there timezones hard-coded into
> PostgreSQL?
Well, the good news is that Unix gets it as right as anyone, and the bad
news is that it isn't so good :/
As far as I know, there is no defined interface to get access to
non-default timezone information on Unix platforms (anyone having more
info is welcome to steer us to the right place). Postgres has a fairly
large table of timezone information (predating my involvement with it)
which is used to parse input time strings, and which can be used for
formatting output time strings for non-default time zones.
btw, when we finish solidifying v6.1, I have a few new time utility
functions ready to go; one of which is date_zone('timezone', datetime)
which will return a time translated to the specified time zone. This
takes advantage of the static timezone info already in Postgres.
- Tom
------------------------------
