Обсуждение: PostgreSQL 8.0.3 : initdb fails with the time zone value WAT0 on HP-Unix platforms

Hello All,

    PostgreSQL-8.0.3 doesnot work with time zone value WAT0 ( for West Africa Time ).
HP Unix 11.23 PA and IPF servers set the time zone value for West Africa Time as "WAT0" in it's "/etc/TIMEZONE" file.

When we try to initialize the database directories using initdb command, we get the following error,

$ initdb -D /var/opt/iexpress/postgresql
The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.

The database cluster will be initialized with locale C.

fixing permissions on existing directory /var/opt/iexpress/postgresql... ok
creating directory /var/opt/iexpress/postgresql/base... ok
creating directory /var/opt/iexpress/postgresql/global... ok
creating directory /var/opt/iexpress/postgresql/pg_xlog... ok
creating directory /var/opt/iexpress/postgresql/pg_clog... ok
selecting default max_connections... 10
selecting default shared_buffers... 50
creating configuration files... ok
creating template1 database in /var/opt/iexpress/postgresql/base/1... FATAL:  invalid value for parameter "timezone":
"WAT0"

initdb: failed

    When we changed the server timezone value to "WAT-01:00" in TZ environment variable
as specified in http://www.postgresql.org/docs/7.4/static/datetime-keywords.html, it worked well.

However it has to be work for time zone value "WAT0", generated by server for West Africa Time.
So possibly this could be the bug with the postgresql. Can you please provide a patch to fx this issue in PostgreSQL
source? 

thanks,
Kathir.


---------------------------------
Yahoo! Mail Mobile
 Take Yahoo! Mail with you! Check email on your mobile phone.

Kathir Velu <kathir_kovai@yahoo.com> writes:
>     PostgreSQL-8.0.3 doesnot work with time zone value WAT0 ( for West Africa Time ).

Hmm, is there someplace where that is actually used?  The zic timezone
database says that WAT generally means GMT+1 not GMT.

> So possibly this could be the bug with the postgresql. Can you please provide a patch to fx this issue in PostgreSQL
source? 

We are not in the business of thinking that we know better than the
people who maintain the timezone database.  I'd suggest taking it up
with the timezone list (tz@elsie.nci.nih.gov) if you think this is
correct and not an error on HP's part.

            regards, tom lane