HELLO:

I have now an error similar to one posted under the subject:

We had format the DISK and reinstall the SO (Red Hat Linux 8.0 3.2-7); we d=
on't have a pg_dumpall file of support; but we have=20
The copy of the data file that was running ok under (PG-8.0.7).
We reinstall P.G 8.0.7 and try to start post-master with the database clust=
er but have this error in the log:

FATAL: invalid value for parameter "lc_messages": "en_US.UTF-8"
FATAL: invalid value for parameter "lc_messages": "en_US.UTF-8"
FATAL: invalid value for parameter "lc_messages": "en_US.UTF-8"

When I change the postgresql.conf file changing en_US.UTF-8 by C; the erro=
r dissapears but show me this another:

FATAL: database files are incompatible with operating system
DETAIL: The database cluster was initialized with LC_COLLATE "en_US.UTF-8"=
, which is not recognized by setlo
cale().
HINT: It looks like you need to initdb or install locale support

When I run:

Locale obtain this:
[root@gene4 data]# locale
LANG=3Den_US.UTF-8
LC_CTYPE=3D"en_US.UTF-8"
LC_NUMERIC=3D"en_US.UTF-8"
LC_TIME=3D"en_US.UTF-8"
LC_COLLATE=3D"en_US.UTF-8"
LC_MONETARY=3D"en_US.UTF-8"
LC_MESSAGES=3D"en_US.UTF-8"
LC_PAPER=3D"en_US.UTF-8"
LC_NAME=3D"en_US.UTF-8"
LC_ADDRESS=3D"en_US.UTF-8"
LC_TELEPHONE=3D"en_US.UTF-8"
LC_MEASUREMENT=3D"en_US.UTF-8"
LC_IDENTIFICATION=3D"en_US.UTF-8"
LC_ALL=3D

But when I locale - a the result is:

[root@gene4 data]# locale -a
C
POSIX
en_AU
en_AU.utf8
en_BW
en_BW.utf8
en_CA
en_CA.utf8
en_DK
en_DK.utf8
en_GB
en_GB.iso885915
en_GB.utf8
en_HK
en_HK.utf8
en_IE
en_IE.utf8
en_IE.utf8@euro
en_IE@euro
en_IN
en_NZ
en_NZ.utf8
en_PH
en_PH.utf8
en_SG
en_SG.utf8
en_US
en_US.iso885915
en_US.utf8
en_ZA
en_ZA.utf8
en_ZW
en_ZW.utf8


I don't see en_US.UTF-8 there why..??

I have tried doing initdb to an empty cluster and copying the data folder =
but the erros is the same.

Could you help me to resolve this..


Thank you very much for your colaboration.


FERNANDO ROJAS
Ingeniero de Sistemas y Computaci=F3n
Unidad de Sistemas de Informaci=F3n
Centro Internacional de Agricultura Tropical (CIAT)
E-mail: frojas (AT) cgiar (DOT) org
Phone57-2)445-01-00 Ext 3647=20

-----Original Message-----
From: pgsql-admin-owner (AT) postgresql (DOT) org [mailtogsql-admin-owner@postgresql=
..org] On Behalf Of Dirk Lutzeb=E4ck
Sent: Friday, June 09, 2006 8:26 AM
To: pgsql-admin (AT) postgresql (DOT) org; pgsql-general (AT) postgresql (DOT) org; pgsql-bugs@po=
stgresql.org
Cc: tgl (AT) sss (DOT) pgh.pa.us
Subject: [ADMIN] How to set the global OID counter? COPY WITH OIDS does not=
set global OID counter?

Hi,

how can one set the global OID counter in 8.1.X? We think it would work in =
8.0.X using the COPY WITH OIDS command but this does not work in 8.1.X anym=
ore.

We have the problem that we made a dump using 'pg_dump -o' in 8.0.X, create=
d a new database in 8.1.X and read back in but the global OID counter staye=
d at 40.000 so OIDs will be allocated again!

Thanks for help,

Dirk

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

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match