Frank,
Of course you could always get brave and recompile the zone files :). I outlined a procedure on my web site:
http://www.postgresqlforums.com/wiki/ If your interested in braving those waters. I did perform it against 8.1.5 and the zone files worked fine with your test case.
Perhaps this is a good excuse to give 8.2 a whirl? :)
On 1/1/07, Tom Lane <tgl@sss.pgh.pa.us> wrote: Frank Bax <fbax@sympatico.ca> writes:
> fbax=> show time zone;
> TimeZone
> ----------------
> Canada/Eastern
Oh, there's your problem: as of 8.1.5's version of the zoneinfo files,
it wasn't clear what Canada was going to do. Looking at our CVS history
it seems the zoneinfo people only did something about it in mid-2006:
+# From Paul Eggert (2006-06-27):
+# For now, assume all of DST-observing Canada will fall into line with the
+# new US DST rules,
This is in CVS for 8.1.6 but not released yet. What I'd suggest is
grabbing the share/timezone/* files out of an 8.2.0 release, which
does have the update. You might be able to get away with just copying
your /usr/share/zoneinfo tree into Postgres' share/timezone directory,
but be prepared to undo that because it could break things entirely:
there's more than one zoneinfo file format out there.
Also note you need to restart the postmaster after updating zoneinfo,
I don't think there's any provision for noticing updates automatically.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
