Thread: 7.4.2 initdb problem

7.4.2 initdb problem

From
"Medora Schauer"
Date:

I’ve installed 7.4.2 on a PowerPC system running linux 2.4.13.  When I try to run initdb to create to create the database cluster I get the following:

 

$ initdb -D $PGDATA

The files belonging to this database system will be owned by user "thebox".

This user must also own the server process.

 

The database cluster will be initialized with locale C.

 

fixing permissions on existing directory /home/thebox/data/database... ok

creating directory /home/thebox/data/database/base... ok

creating directory /home/thebox/data/database/global... ok

creating directory /home/thebox/data/database/pg_xlog... ok

creating directory /home/thebox/data/database/pg_clog... ok

selecting default max_connections... 100

selecting default shared_buffers... 1000

creating configuration files... ok

creating template1 database in /home/thebox/data/database/base/1... ok

initializing pg_shadow... ok

enabling unlimited row size for system tables... ok

initializing pg_depend... ok

creating system views... ok

loading pg_description... ok

creating conversions... ERROR:  could not load library "/usr/local/pgsql-7.4.2/lib/ascii_and_mic.so": /usr/local/pgsql-7.4.2/lib/ascii_and_mic.so: undefined symbol: pg_mic2ascii

/usr/local/pgsql/bin/initdb: line 842: 11792 Broken pipe             grep -v '^DROP CONVERSION' $datadir/conversion_create.sql

     11793 Done(1)                 | "$PGPATH"/postgres $PGSQL_OPT template1 >/dev/null

 

initdb: failed

 

I’m at a loss as to where I should look for the problem. 

 

Any guidance will be greatly appreciated,

 

Medora Schauer

 

 

Re: 7.4.2 initdb problem

From
Tom Lane
Date:
"Medora Schauer" <mschauer@fairfield.com> writes:
> creating conversions... ERROR:  could not load library
> "/usr/local/pgsql-7.4.2/lib/ascii_and_mic.so":
> /usr/local/pgsql-7.4.2/lib/ascii_and_mic.so: undefined symbol:
> pg_mic2ascii

Hm, that's odd.  The pg_mic2ascii function is defined in the main
backend, so it certainly should be available to ascii_and_mic.so.
Is it possible the postgres executable has been stripped, or some
such strange move?  Did you build Postgres yourself or use someone
else's RPM, and if so whose?

            regards, tom lane