 | |
Re: beta3 winxp initdb problems
comp.databases.postgresql.general comp.databases.postgresql.general
 |
| | Thread Tools | Display Modes |
#1
 
| |||
| |||
|
Re: beta3 winxp initdb problems -
10-14-2004
, 02:17 AM
|
Hello, folks, I am trying to install pgsql8 on winxp. I tried first to install "as is" with pginstaller beta2-dev3, no luck, it froze, switched off Nod32, froze a little later, ran through the list of services, switched off anything that seemed to be a firewall, no luck. So I compiled beta3 with mingw, installed, and now initdb keeps telling me this: listing Microsoft Windows XP [Verzia 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\WINDOWS\system32>d: snip/ D:\tmp\data>initdb The files belonging to this database system will be owned by user "postgresql". This user must also own the server process. The database cluster will be initialized with locale Slovak_Slovakia.1250. fixing permissions on existing directory d:/tmp/data ... ok creating directory d:/tmp/data/global ... ok creating directory d:/tmp/data/pg_xlog ... ok creating directory d:/tmp/data/pg_xlog/archive_status ... ok creating directory d:/tmp/data/pg_clog ... ok creating directory d:/tmp/data/pg_subtrans ... ok creating directory d:/tmp/data/base ... ok creating directory d:/tmp/data/base/1 ... ok creating directory d:/tmp/data/pg_tblspc ... ok selecting default max_connections ... 10 selecting default shared_buffers ... 50 creating configuration files ... ok creating template1 database in d:/tmp/data/base/1 ... 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. child process was terminated by signal 1 initdb: failed initdb: removing contents of data directory "d:/tmp/data" D:\tmp\data /listing now, beta2 reported no problems with initdb, it just never finished the installation and even if I tell my computer I am located in London, UK, use Greenwich Mean Time, I still get this fatal error. |
Could you please run this with debugging enabled? You do this by passing "-d" to initdb.
The interesting output is the stuff that comes between the "creating template1 database" message and the FATAL error.
Did you restart the commandprompt you ran initdb in after changing the timezone?
//Magnus
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
#2
| |||
| |||
|
|
Hello, folks, I am trying to install pgsql8 on winxp. I tried first to install "as is" with pginstaller beta2-dev3, no luck, it froze, switched off Nod32, froze a little later, ran through the list of services, switched off anything that seemed to be a firewall, no luck. So I compiled beta3 with mingw, installed, and now initdb keeps telling me this: listing Microsoft Windows XP [Verzia 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\WINDOWS\system32>d: snip/ D:\tmp\data>initdb The files belonging to this database system will be owned by user "postgresql". This user must also own the server process. The database cluster will be initialized with locale Slovak_Slovakia.1250. fixing permissions on existing directory d:/tmp/data ... ok creating directory d:/tmp/data/global ... ok creating directory d:/tmp/data/pg_xlog ... ok creating directory d:/tmp/data/pg_xlog/archive_status ... ok creating directory d:/tmp/data/pg_clog ... ok creating directory d:/tmp/data/pg_subtrans ... ok creating directory d:/tmp/data/base ... ok creating directory d:/tmp/data/base/1 ... ok creating directory d:/tmp/data/pg_tblspc ... ok selecting default max_connections ... 10 selecting default shared_buffers ... 50 creating configuration files ... ok creating template1 database in d:/tmp/data/base/1 ... 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. child process was terminated by signal 1 initdb: failed initdb: removing contents of data directory "d:/tmp/data" D:\tmp\data /listing now, beta2 reported no problems with initdb, it just never finished the installation and even if I tell my computer I am located in London, UK, use Greenwich Mean Time, I still get this fatal error. I have no idea what to do... please, give me some advice. Thanks in advance Zoltan ====================== REKLAMA ======================== Spolocnost SUN Microsystems uviedla na trh novy server Sun Fire V20z zalozeny procesoroch AMD Opteron. Viac informacii najdete na : http://www.somi.sk/sun/v20z.php ================================================== ===== ---------------------------(end of broadcast)--------------------------- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to majordomo (AT) postgresql (DOT) org) |
---------------------------(end of broadcast)---------------------------
TIP 3: 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
#3
| |||
| |||
|
|
-----Original Message----- From: bartkoedith (AT) internetkosice (DOT) sk [mailto:bartkoedith (AT) internetkosice (DOT) sk] Sent: Thursday, October 14, 2004 9:34 AM To: pgsql-general (AT) postgresql (DOT) org Cc: Magnus Hagander Subject: Re: [GENERAL] beta3 winxp initdb problems Magnus, et al., This is, what initdb -d says: listing D:\tmp\data>initdb -d Running in debug mode. VERSION=8.0.0beta3 PGDATA=d:/tmp/data share_path=c:/msys/1.0/share/postgresql PGPATH=c:/msys/1.0/bin POSTGRES_SUPERUSERNAME=postgresql POSTGRES_BKI=c:/msys/1.0/share/postgresql/postgres.bki POSTGRES_DESCR=c:/msys/1.0/share/postgresql/postgres.description POSTGRESQL_CONF_SAMPLE=c:/msys/1.0/share/postgresql/postgresql .conf.sample PG_HBA_SAMPLE=c:/msys/1.0/share/postgresql/pg_hba.conf.sample PG_IDENT_SAMPLE=c:/msys/1.0/share/postgresql/pg_ident.conf.sample The files belonging to this database system will be owned by user "postgresql". This user must also own the server process. The database cluster will be initialized with locale Slovak_Slovakia.1250. fixing permissions on existing directory d:/tmp/data ... ok creating directory d:/tmp/data/global ... ok creating directory d:/tmp/data/pg_xlog ... ok creating directory d:/tmp/data/pg_xlog/archive_status ... ok creating directory d:/tmp/data/pg_clog ... ok creating directory d:/tmp/data/pg_subtrans ... ok creating directory d:/tmp/data/base ... ok creating directory d:/tmp/data/base/1 ... ok creating directory d:/tmp/data/pg_tblspc ... ok selecting default max_connections ... 10 selecting default shared_buffers ... 50 creating configuration files ... ok creating template1 database in d:/tmp/data/base/1 ... DEBUG: TZ "Europe/Belgrad e" matches Windows timezone "Central Europe Daylight Time" 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) DEBUG: shmem_exit(1) DEBUG: exit(1) child process was terminated by signal 1 initdb: failed initdb: removing contents of data directory "d:/tmp/data" D:\tmp\data /listing So I said to myself, set the timezone to GMT. This, what I got after switching off the automatic daylight saving time notification: listing D:\tmp\data>initdb -d Running in debug mode. VERSION=8.0.0beta3 PGDATA=d:/tmp/data share_path=c:/msys/1.0/share/postgresql PGPATH=c:/msys/1.0/bin POSTGRES_SUPERUSERNAME=postgresql POSTGRES_BKI=c:/msys/1.0/share/postgresql/postgres.bki POSTGRES_DESCR=c:/msys/1.0/share/postgresql/postgres.description POSTGRESQL_CONF_SAMPLE=c:/msys/1.0/share/postgresql/postgresql .conf.sample PG_HBA_SAMPLE=c:/msys/1.0/share/postgresql/pg_hba.conf.sample PG_IDENT_SAMPLE=c:/msys/1.0/share/postgresql/pg_ident.conf.sample The files belonging to this database system will be owned by user "postgresql". This user must also own the server process. The database cluster will be initialized with locale Slovak_Slovakia.1250. fixing permissions on existing directory d:/tmp/data ... ok creating directory d:/tmp/data/global ... ok creating directory d:/tmp/data/pg_xlog ... ok creating directory d:/tmp/data/pg_xlog/archive_status ... ok creating directory d:/tmp/data/pg_clog ... ok creating directory d:/tmp/data/pg_subtrans ... ok creating directory d:/tmp/data/base ... ok creating directory d:/tmp/data/base/1 ... ok creating directory d:/tmp/data/pg_tblspc ... ok selecting default max_connections ... 10 selecting default shared_buffers ... 50 creating configuration files ... ok creating template1 database in d:/tmp/data/base/1 ... DEBUG: TZ "Europe/Dublin" matches Windows timezone "GMT Standard Time" 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) DEBUG: shmem_exit(1) DEBUG: exit(1) child process was terminated by signal 1 initdb: failed initdb: removing contents of data directory "d:/tmp/data" D:\tmp\data /listing Any ideas? Zoltan Hello! Could you please run this with debugging enabled? You do this by passing "-d" to initdb. The interesting output is the stuff that comes between the "creating template1 database" message and the FATAL error. Did you restart the commandprompt you ran initdb in after changing the timezone? //Magnus ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster |
TIP 3: 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
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.