From: | source <source(at)celasmaya(dot)edu(dot)gt> |
---|---|
To: | tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-general(at)postgresql(dot)org |
Subject: | Re:Re: initdb & multibyte |
Date: | 2000-10-11 15:31:21 |
Message-ID: | MailDropW951.5b4.1001011093121@10.0.0.120 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)celasmaya(dot)edu(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Giorgio Ponza | 2000-10-11 15:37:01 | R: PostgreSQL book |
Previous Message | Ingram, Bryan | 2000-10-11 15:26:57 | decoding pg_log |