The following bug has been logged online:
Bug reference: 1271
Logged by: Ramzi Fadel
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0 Beta
Operating system: Windows XP Prof, 5.1.2600 Build 2600
Description: Installation problems (cannot execute initdb.exe)
Details:
The installation file: postgresql-8.0-beta2-dev3.msi
Error log; see below.
Steps taken:
- Run the installation with a administrator user (I do expect the
installation to complete!)
- The installation creates an user for the service named "postrunner"
- Log off
- Log in with the "postrunner" user
- Run the installation. The installation fails during creation of the
cluster, see below:
-------------------------------
Initdb.log:
-------------------------------
The files belonging to this database system will be owned by user "raf".
This user must also own the server process.
The database cluster will be initialized with locale C.
fixing permissions on existing directory C:/PGSQL80/data ... ok
creating directory C:/PGSQL80/data/global ... ok
creating directory C:/PGSQL80/data/pg_xlog ... ok
creating directory C:/PGSQL80/data/pg_xlog/archive_status ... ok
creating directory C:/PGSQL80/data/pg_clog ... ok
creating directory C:/PGSQL80/data/pg_subtrans ... ok
creating directory C:/PGSQL80/data/base ... ok
creating directory C:/PGSQL80/data/base/1 ... ok
creating directory C:/PGSQL80/data/pg_tblspc ... ok
selecting default max_connections ... 10
selecting default shared_buffers ... 50
creating configuration files ... ok
creating template1 database in C:/PGSQL80/data/base/1 ... execution of
PostgreSQL by a user with administrative permissions is not permitted.
The server must be started under an unprivileged user ID to prevent
possible system security compromise. See the documentation for
more information on how to properly start the server.
child process was terminated by signal 1
initdb: failed
initdb: removing contents of data directory "C:/PGSQL80/data"
---------------------------(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
