Re: Need Help Recovering from Botched Upgrade Attempt - Mailing list pgsql-general

From Rich Shepard
Subject Re: Need Help Recovering from Botched Upgrade Attempt
Date
Msg-id Pine.LNX.4.64.0806171913440.11116@salmo.appl-ecosys.com
Whole thread Raw
In response to Re: Need Help Recovering from Botched Upgrade Attempt  (Klint Gore <kgore4@une.edu.au>)
Responses Re: Need Help Recovering from Botched Upgrade Attempt  (Adrian Klaver <aklaver@comcast.net>)
Re: Need Help Recovering from Botched Upgrade Attempt  (Klint Gore <kgore4@une.edu.au>)
List pgsql-general
On Wed, 18 Jun 2008, Klint Gore wrote:

>>    5.) Built postgresql-8.3.3 using the SlackBuild script, then ran
>> 'upgradepkg postgresql-8.3.3*tgz'; other than reporting not finding an
>> expected pid file, that went smoothly.
>>
> Is there an initdb in here somewhere?  Or is the 8.3 server trying to start
> with an 8.1 file structure?

Klint,

   Backed up a couple of steps, and tried again. Removed postgresql-8.3.3;
deleted all contents of /var/lib/pgsql/data (because initdb is supposed to
create the contents, if I correctly read the Postgresql book); re-installed
postgresql-8.3.3; ran (as user postgres) 'initdb -D /var/lib/pgsql/data'.
Nothing!

   I've really FUBARed this and don't understand how, or what to do to
recover.

Thanks,

Rich

--
Richard B. Shepard, Ph.D.               |  Integrity            Credibility
Applied Ecosystem Services, Inc.        |            Innovation
<http://www.appl-ecosys.com>     Voice: 503-667-4517      Fax: 503-667-8863

pgsql-general by date:

Previous
From: Rich Shepard
Date:
Subject: Re: Need Help Recovering from Botched Upgrade Attempt
Next
From: Adrian Klaver
Date:
Subject: Re: Need Help Recovering from Botched Upgrade Attempt