Thread: 7.3RC2 install woes

I have gotten 7.3RC2 finally installed but I am having troubles getting
it to run ...

I did an initdb and then tried to start the postmast but got the
following erro when trying to start the postmaster:

postgres@localhost pgsql7.3RC2]$ bin/initdb -D -E EUC_JP
/usr/local/pgsql7.3RC2/data
The files belonging to this database system will be owned by user
"postgres".
This user must also own the server process.

The database cluster will be initialized with locale en_US.ja_JP.eucJP.
[..]

Failed to initialize lc_messages to ''
ok
creating configuration files... ok
initializing pg_shadow... Failed to initialize lc_messages to ''
ok
enabling unlimited row size for system tables... Failed to initialize
lc_messages to ''
ok
initializing pg_depend... Failed to initialize lc_messages to ''
ok
creating system views... Failed to initialize lc_messages to ''
ok
loading pg_description... Failed to initialize lc_messages to ''
ok
creating conversions... Failed to initialize lc_messages to ''
ok
setting privileges on built-in objects... Failed to initialize
lc_messages to ''
ok
vacuuming database template1... Failed to initialize lc_messages to ''
ok
copying template1 to template0... Failed to initialize lc_messages to ''
ok

Success. You can now start the database server using:

     bin/postmaster -D /usr/local/pgsql7.3RC2/data
or
     bin/pg_ctl -D /usr/local/pgsql7.3RC2/data -l logfile start

[postgres@localhost pgsql7.3RC2]$ bin/pg_ctl -D
/usr/local/pgsql7.3RC2/data start
postmaster successfully started
Failed to initialize lc_messages to ''
FATAL:  invalid value for option 'LC_MESSAGES': 'en_US.ja_JP.eucJP'

Seems postgres doesn't like me setting the encoding to EUC_JP?

Jc

Jean-Christian Imbeault <jc@mega-bucks.co.jp> writes:
> I did an initdb and then tried to start the postmast but got the
> following erro when trying to start the postmaster:

> Failed to initialize lc_messages to ''
> FATAL:  invalid value for option 'LC_MESSAGES': 'en_US.ja_JP.eucJP'

> Seems postgres doesn't like me setting the encoding to EUC_JP?

Not Postgres: your platform isn't happy with that setting of
LC_MESSAGES.  (This is not the first report we've seen of platforms
that reject a locale code for LC_MESSAGES that they support for other
LC_ settings :-()

You could fix this by editing the setting of lc_messages in
postgresql.conf to be something that your system will accept.

            regards, tom lane

Tom Lane wrote:

 > Not Postgres: your platform isn't happy with that setting of
 > LC_MESSAGES.  (This is not the first report we've seen of platforms
 > that reject a locale code for LC_MESSAGES that they support for other
 > LC_ settings :-()

I figured as much. I have never been able to set up a RH Linux machine
that never had locale problem with perl -v ...

I did solve the problem my manually doing:

export LC_MESSAGES='C'
export LC_MONETARY='C'
export LC_NUMERIC='C'
export LC_TIME='C'

Don't know if it's the recommended way or not but it worked as far as
getting initdb to work and starting up the DB.

I'm hoping that this won't have any adverse affect on my DB. The only
thing that really needs to be in japanese is the text so I'm assuming
everything should be fine ...

Jc