pgsql-server: Check more test points (in fact, every week in 1970..2004)
Log Message:
-----------
Check more test points (in fact, every week in 1970..2004) to get a more
accurate matching of our time zone to the system's zone. This method is
able to distinguish Antarctica/Casey from Australia/Perth, as in Chris
K-L's recent example; and it is not materially slower than before, because
the extra checks generally don't get done against very many time zones.
It seems possible that with this test we'd be able to correctly identify
Windows timezones without looking at the timezone name, but I do not
have the ability to try it.
Modified Files:
--------------
pgsql-server/src/timezone:
pgtz.c (r1.17 -> r1.18)
(http://developer.postgresql.org/cvsweb.cgi/pgsql-server/src/timezone/pgtz.c.diff?r1=1.17&r2=1.18)
Cool, that fixes the detection for me.
Chris
Tom Lane wrote:
Show quoted text
Log Message:
-----------
Check more test points (in fact, every week in 1970..2004) to get a more
accurate matching of our time zone to the system's zone. This method is
able to distinguish Antarctica/Casey from Australia/Perth, as in Chris
K-L's recent example; and it is not materially slower than before, because
the extra checks generally don't get done against very many time zones.It seems possible that with this test we'd be able to correctly identify
Windows timezones without looking at the timezone name, but I do not
have the ability to try it.Modified Files:
--------------
pgsql-server/src/timezone:
pgtz.c (r1.17 -> r1.18)
(http://developer.postgresql.org/cvsweb.cgi/pgsql-server/src/timezone/pgtz.c.diff?r1=1.17&r2=1.18)---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster