Postgres Pro
Downloads
Home   >   mailing lists

Starting Back End - Mailing list pgsql-admin

From Rojas, Fernando \(CIAT\)
Subject Starting Back End
Date
Msg-id AACD86431269C546A6ECF51213C910D8133F9D@ciatex8.CIAT.CGIARAD.ORG
Whole thread Raw
List pgsql-admin
Tree view

We had format the DISK and reinstall the SO (Red Hat Linux 8.0 3.2-7); we don't have a pg_dumpall file of support; but we have

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 cluster 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 error 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=en_US.UTF-8

LC_CTYPE="en_US.UTF-8"

LC_NUMERIC="en_US.UTF-8"

LC_TIME="en_US.UTF-8"

LC_COLLATE="en_US.UTF-8"

LC_MONETARY="en_US.UTF-8"

LC_MESSAGES="en_US.UTF-8"

LC_PAPER="en_US.UTF-8"

LC_NAME="en_US.UTF-8"

LC_ADDRESS="en_US.UTF-8"

LC_TELEPHONE="en_US.UTF-8"

LC_MEASUREMENT="en_US.UTF-8"

LC_IDENTIFICATION="en_US.UTF-8"

LC_ALL=

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.


From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of renneyt@yahoo.com
Sent: Tuesday, June 13, 2006 3:29 PM
To: Jim C. Nasby
Cc: postgres
Subject: Re: [ADMIN] pg_dump/restore problem

Jim C. Nasby wrote: 
On Mon, Jun 12, 2006 at 04:51:18PM -0400, renneyt@yahoo.com wrote: 
I am trying to move some data from an 8.0.7 instance to a 7.4.8 
instance. I did a pg_dump and then did a pg_restore.
For the most part the data transferred through to the older instance but 
I had problems with the sequence updates.

SELECT pg_catalog.setval(pg_catalog.pg_get_serial_sequence('nw_foo', 
'foo_id'), 678, true);
ERROR:  function pg_catalog.pg_get_serial_sequence("unknown", "unknown") 
does not exist
HINT:  No function matches the given name and argument types. You may 
need to add explicit type casts.

I am looking for a an alternative to manually issuing alter sequence 
commands.   
>From http://www.postgresql.org/docs/8.1/interactive/release-8-0.html:

# Add pg_get_serial_sequence() to return a SERIAL column's sequence name
(Christopher)


Does  pg_get_serial_sequence()  exist as plpgsql code? Where may I find it? I would like to retrofit it into a 7.4.8 PG database.

Thanks


This allows automated scripts to reliably find the SERIAL sequence name. 

If you use a 7.x copy of pg_dump it might work, though there could be
catalog changes that make that a problem.

pgsql-admin by date:

Previous
From: David
Date:
Subject: Re: password authentication failed (postgresql v8.1.4)
Next
From: "Rojas, Fernando \(CIAT\)"
Date:
Subject: FW: Error starting backend