Hello,

finally the problem is solved. The problem was with locales.

I installed and initialised the database under cs_CZ, so Pg
recorded cs_CZ in all its configurations and startup scripts.
After that I changed /etc/sysconfig/i18n to use en_US locale as
system default.
And that was the problem. According to "ps axe" the postmaster was
running under en_US locales instead of cs_CZ as I expected.
So I changed /etc/sysconfig/i18n to use cs_CZ and everything is ok
from then. All indexes seem to be working fine and there are no problems.

But I would like to know why it was not started under cs_CZ when
all Pg config files specify cs_CZ and ~postgres/.bash_profile contains
export LANG="cs_CZ" and postmaster is run from it's rc script as

su -l postgres -s /bin/sh -c "/usr/bin/pg_ctl -D $PGDATA ...."

So I expected that cs_CZ will be used in this case. :-( GRrrrrr.

Ok now it's working, thank you all who helped.

Martin

--

Martin Edlman
Fortech s.r.o, Litomysl
Public PGP key: http://edas.visaci.cz/#keys


---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

Martin Edlman <edlman (AT) fortech (DOT) cz> writes:
"ps" is not a reliable guide to the locale settings being used by
Postgres.

The postmaster will adopt LC_COLLATE and LC_CTYPE from the settings
recorded in pg_control (by initdb) regardless of its environment.
Other, noncritical, settings such as LC_MESSAGES are taken from
postgresql.conf if specified there. The environment values reported by
"ps" would only be used for noncritical settings, and then only if
not overridden by postgresql.conf.

So I'm not convinced that you've correctly identified the problem.
However, it seems possible that part of the issue is misbehavior if
the various LC_xxx settings aren't all alike --- could you dig further
and try to isolate it?

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings

Maybe it's RedHat related, I don't know.
When I had en_US in /etc/sysconfig/i18n and cs_CZ in
~postgres/.bash_profile and when I did (as root) `su - postgres -s /bin/sh
-c "echo $LANG"' I saw LANG=en_US (!!!), when I did `su - postgres' and
then `echo $LANG' (as postgres) I saw LANG=cs_CZ.
So I believe that ps gives correct info and I believe that postmaster was
running with en_US locales. It seems that the problem is with `su' which
may not run user's .bash* scripts when executing command with -c.

That's what I was hoping for, but unfortunately I didn't work this way.

I isolated the problem when trying Pg on different HW. I installed RH from
install CD and fortunatelly installed it with cs_CZ as default. Then
evertyhing worked - the same Pg, the same database. After that I looked at
`ps axe' and saw the difference in LANG.

I set ALL LC_xxx variables to cs_CZ in postgres.conf but it didn't help.
Only setting LANG to cs_CZ in systemwide settings.

Regards, Martin

--

Martin Edlman
Fortech s.r.o, Litomysl
Public PGP key: http://edas.visaci.cz/#keys


---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo (AT) postgresql (DOT) org)