Never seen this one. Can you run it with debugging enabled (-d option to
initdb) and see if it gives you any more data.

Are you doing something different as compared to the initdb the MSI did?
Different encoding or such?

//Magnus

>-----Original Message-----
>From: [EMAIL PROTECTED] 
>[mailto:[EMAIL PROTECTED] On Behalf Of Christoph Becker
>Sent: den 12 januari 2005 19:59
>To: pgsql-bugs@postgresql.org
>Subject: [BUGS] rc5: initdb freeze with "selecting default 
>max_connections ..."
>
>
>System is Windows XP, the postgres-installer (postgresql-8.0.0-rc5.zip 
>resp. .msi) was used to install
>envirement variable PGDATA is set to g:\pgsql
>
>Never before (7.x versions, older version 8 beta/rc) I have got the 
>following response/problem with an initdb:
>
>C:\Programme\PostgreSQL\8.0.0-rc5\bin>initdb
>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 
>German_Germany.1252.
>
>creating directory G:/pgsql/data ... ok
>creating directory G:/pgsql/data/global ... ok
>creating directory G:/pgsql/data/pg_xlog ... ok
>creating directory G:/pgsql/data/pg_xlog/archive_status ... ok
>creating directory G:/pgsql/data/pg_clog ... ok
>creating directory G:/pgsql/data/pg_subtrans ... ok
>creating directory G:/pgsql/data/base ... ok
>creating directory G:/pgsql/data/base/1 ... ok
>creating directory G:/pgsql/data/pg_tblspc ... ok
>selecting default max_connections ...
>
>At this point initdb did freeze time and again.
>However, before initdb seemed to have worked, when it was used by the 
>PostgreSQL-Windows-Installer.
>
>Regards
>Christoph Becker
>
>
>
>---------------------------(end of 
>broadcast)---------------------------
>TIP 5: Have you checked our extensive FAQ?
>
>               http://www.postgresql.org/docs/faqs/FAQ.html
>

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

               http://www.postgresql.org/docs/faqs/FAQ.html

Reply via email to