The following bug has been logged online:

Bug reference: 2798
Logged by: Daniel Baldoni
Email address: pgsql (AT) lcds (DOT) com.au
PostgreSQL version: 8.2rc
Operating system: Any
Description: Obsolete tiemzone data included
Details:

G'day folks,

This may not qualify as a "bug", but the timezone data included with the
8.2rc tarballs is out of date. Will the (at-the-time-of-release) "current"
version be included with the 8.2 production version?

Ciao.

PS: Yes, I realise keeping timezone data up-to-date is
an ongoing battle.

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo (AT) postgresql (DOT) org so that your
message can get through to the mailing list cleanly

Daniel Baldoni wrote:
The CVS head has been updated to the latest "tzdata2006p" version of
the timezone data, so it should be fixed in the next RC.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

Daniel Baldoni wrote:
Post-rc1 we upgraded it again:

date: 2006/11/28 19:37:03; author: tgl; state: Exp; lines: +18 -8
Update timezone data to tzdata2006p zic distribution. It seems Western
Australia decided to institute DST with one month's notice ... way to
go, politicians.

We do not guarantee that we will always ship the most recent timezone
database version, however.

--
Bruce Momjian bruce (AT) momjian (DOT) us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

---------------------------(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