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

Thu, 29 Jul 2004 09:14:52 -0400
"Merlin Moncure" <merlin.moncure@rcsonline.com>
win32 crash in initdb
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>
To: <pgsql-hackers-win32@postgresql.org>
Cc: <pgsql-hackers@postgresql.org>
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
> 






initdb debug messages are here.
 
---
.....
creating configuration files ... okcreating 
template1 database in data/base/1 ... LOG:  could not open directory 
"/share/timezone": No such file or directoryLOG:  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 timezoneDETAIL:  It appears that your GMT time zone 
uses leap seconds. PostgreSQL does not 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>
To: <pgsql-hackers-win32@postgresql.org>
Cc: <pgsql-hackers@postgresql.org>
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>
Thu, 29 Jul 2004 23:06:17 +0900
"Korea PostgreSQL Users' Group" <pgsql-kr@postgresql.or.kr>
Re: win32 crash in initdb - it has still problems.
"Merlin Moncure" <merlin.moncure@rcsonline.com> writes:
> The crash people are getting in initdb is due to the 1.19 revision to
> pgtz.c.  Not sure why yet...looking into it...

Unfortunate behavior when probing pre-1970 dates, maybe?

			regards, tom lane

Thu, 29 Jul 2004 10:49:46 -0400
Tom Lane <tgl@sss.pgh.pa.us>
Re: [HACKERS] win32 crash in initdb 