Re: Need Help Recovering from Botched Upgrade Attempt

Поиск
Список
Период
Сортировка
Искать
От
Rich Shepard
Тема
Re: Need Help Recovering from Botched Upgrade Attempt
Дата
Msg-id
Pine.LNX.4.64.0806171819130.11116@salmo.appl-ecosys.com
Ответ на
Список
Дерево обсуждения
Need Help Recovering from Botched Upgrade Attempt Rich Shepard <rshepard@appl-ecosys.com>
Re: Need Help Recovering from Botched Upgrade Attempt Klint Gore <kgore4@une.edu.au>
Re: Need Help Recovering from Botched Upgrade Attempt Craig Ringer <craig@postnewspapers.com.au>
Re: Need Help Recovering from Botched Upgrade Attempt Rich Shepard <rshepard@appl-ecosys.com>
Re: Need Help Recovering from Botched Upgrade Attempt Craig Ringer <craig@postnewspapers.com.au>
Re: Need Help Recovering from Botched Upgrade Attempt Alan Hodgson <ahodgson@simkin.ca>
Re: Need Help Recovering from Botched Upgrade Attempt Craig Ringer <craig@postnewspapers.com.au>
Understanding fsync (was: Need Help Recovering from Botched Upgrade Attempt) Sam Mason <sam@samason.me.uk>
Re: Understanding fsync (was: Need Help Recovering from Botched Upgrade Attempt) Greg Smith <gsmith@gregsmith.com>
Re: Understanding fsync (was: Need Help Recovering from Botched Upgrade Attempt) Sam Mason <sam@samason.me.uk>
Re: Understanding fsync Craig Ringer <craig@postnewspapers.com.au>
Re: Understanding fsync Sam Mason <sam@samason.me.uk>
Re: Need Help Recovering from Botched Upgrade Attempt Rich Shepard <rshepard@appl-ecosys.com>
Re: Need Help Recovering from Botched Upgrade Attempt Sam Mason <sam@samason.me.uk>
Re: Need Help Recovering from Botched Upgrade Attempt Rich Shepard <rshepard@appl-ecosys.com>
Re: Need Help Recovering from Botched Upgrade Attempt Rich Shepard <rshepard@appl-ecosys.com>
Re: Need Help Recovering from Botched Upgrade Attempt Rich Shepard <rshepard@appl-ecosys.com>
Re: Need Help Recovering from Botched Upgrade Attempt Adrian Klaver <aklaver@comcast.net>
Re: Need Help Recovering from Botched Upgrade Attempt Rich Shepard <rshepard@appl-ecosys.com>
Re: Need Help Recovering from Botched Upgrade Attempt Klint Gore <kgore4@une.edu.au>
Re: Need Help Recovering from Botched Upgrade Attempt Rich Shepard <rshepard@appl-ecosys.com>
On Wed, 18 Jun 2008, Klint Gore wrote:

> You copied the files without stopping the database?  move 4 to 2.

Klint,

   Yes, actually. There was no activity on any of the databases.

> Is there an initdb in here somewhere?  Or is the 8.3 server trying to start 
> with an 8.1 file structure?

   Ah, yes. I missed stating that. I switched to user postgres and ran:

postgres@salmo:/var/lib/pgsql$ initdb -D ./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 locales
   COLLATE:  C
   CTYPE:    en_US
   MESSAGES: en_US
   MONETARY: en_US
   NUMERIC:  en_US
   TIME:     en_US
could not determine encoding for locale "en_US": codeset is "ANSI_X3.4-1968"
initdb: could not find suitable encoding for locale en_US
Rerun initdb with the -E option.
Try "initdb --help" for more information.

   But, using the -E option with en_US tells me that it's not a valid locale.

Thanks,

Rich

-- 
Richard B. Shepard, Ph.D.               |  Integrity            Credibility
Applied Ecosystem Services, Inc.        |            Innovation
     Voice: 503-667-4517      Fax: 503-667-8863
В списке pgsql-general по дате отправления
От: Laurent Birtz
Дата:
Сообщение: Forcibly vacating locks
От: Rich Shepard
Дата:
FAQ