| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | source <source(at)celasmaya(dot)edu(dot)gt> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: initdb & multibyte |
| Date: | 2000-10-11 15:11:28 |
| Message-ID: | 22871.971277088@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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 | Ingram, Bryan | 2000-10-11 15:26:57 | decoding pg_log |
| Previous Message | Bob Hartung | 2000-10-11 15:07:39 | directory mapping RH with RPM vs RH with tar.z install |