Re: [pgsql-hackers-win32] Weird new time zone - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [pgsql-hackers-win32] Weird new time zone
Date
Msg-id 20804.1089989052@sss.pgh.pa.us
Whole thread Raw
In response to Re: [pgsql-hackers-win32] Weird new time zone  ("Magnus Hagander" <mha@sollentuna.net>)
List pgsql-hackers
"Magnus Hagander" <mha@sollentuna.net> writes:
>> At the moment I like Oliver Jowett's idea of defining "best" 
>> as "the one that matches furthest back".

> Sounds reasonable to me. As long as a clear warning is put in the log
> whenever something is picked that is not a perfect match,

Define "perfect match".  I do not think we can really tell if we have an
exact match or not; the libc timezone API is just too limited to be
sure.  And on many platforms we can be sure we will never have an exact
match, especially if we look at years before 1970.

If you want something in the log I'd be inclined to just always make a
log entry when we infer a timezone setting.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Point in Time Recovery
Next
From: Tom Lane
Date:
Subject: Re: Point in Time Recovery