Re:Re: initdb & multibyte - Mailing list pgsql-general

From source
Subject Re:Re: initdb & multibyte
Date
Msg-id MailDropW951.5b4.1001011093121@10.0.0.120
Whole thread Raw
In response to initdb & multibyte  (source <source@celasmaya.edu.gt>)
Responses Re: initdb & multibyte  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
OK, now we get:

/usr/local/pgsql/bin/pg_encoding: error in loading shared libraries:
/usr/local/pgsql/bin/pg_encoding: undefined symbol: pg_char_to_encoding
initdb: pg_encoding failed

Perhaps you did not configure PostgreSQL for multibyte support or
the program was not successfully installed.


----------
source <source@celasmaya.edu.gt> writes:
> We get the error:
> initdb: pg_encoding failed

Hmm.  Someone else told me about seeing the same thing on a Linux box,
but I didn't hear what the resolution was.

initdb is not very good about giving you details about failures of
the programs it calls --- in particular, pg_encoding's stdout/stderr
is rerouted to /dev/null in the script :-(.  I'd recommend changing
the initdb script to not redirect pg_encoding's output, and then
you'll be able to see what pg_encoding is unhappy about.  Let us know...

            regards, tom lane


pgsql-general by date:

Previous
From: "Ingram, Bryan"
Date:
Subject: decoding pg_log
Next
From: "Giorgio Ponza"
Date:
Subject: R: PostgreSQL book