Re: win32 crash in initdb - it has still problems. - Mailing list pgsql-hackers-win32

From Korea PostgreSQL Users' Group
Subject Re: win32 crash in initdb - it has still problems.
Date
Msg-id 000801c47575$37e64dc0$cdcb56dc@paolo.net
Whole thread Raw
List pgsql-hackers-win32

initdb debug messages are here.
 
---
.....
creating configuration files ... ok
creating template1 database in data/base/1 ... LOG:  could not open directory "/
share/timezone": No such file or directory
LOG:  unable to determine system timezone, defaulting to "GMT"
HINT:  You can specify the correct timezone in postgresql.conf.
FATAL:  could not select a suitable default timezone
DETAIL:  It appears that your GMT time zone uses leap seconds. PostgreSQL does n
ot support leap seconds.
DEBUG:  proc_exit(1)
.....
--------
 
LOG:  could not open directory "/share/timezone": No such file or directory
This message is due to my_exec_path is empty. I don't know where this variable set.
 
another problem,
localizational time zone name (%Z of localtime()) and server time zone name of pg_localtime() are different in CJK OS. (ex. 대한민국 표준시 vis KST)
 
 
 
 
 
----- Original Message -----
From: "Merlin Moncure" <merlin.moncure@rcsonline.com>
Sent: Thursday, July 29, 2004 10:14 PM
Subject: [pgsql-hackers-win32] win32 crash in initdb

> The crash people are getting in initdb is due to the 1.19 revision to
> pgtz.c.  Not sure why yet...looking into it...
>
> Merlin
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to
majordomo@postgresql.org
>

pgsql-hackers-win32 by date:

Previous
From: "Merlin Moncure"
Date:
Subject: Re: Older snapshots
Next
From: Tom Lane
Date:
Subject: Re: Logger subprocess for win32