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

From Klint Gore
Subject Re: Need Help Recovering from Botched Upgrade Attempt
Date
Msg-id 485874A9.7020408@une.edu.au
Whole thread Raw
In response to Re: Need Help Recovering from Botched Upgrade Attempt  (Rich Shepard <rshepard@appl-ecosys.com>)
Responses Re: Need Help Recovering from Botched Upgrade Attempt  (Rich Shepard <rshepard@appl-ecosys.com>)
List pgsql-general
Rich Shepard wrote:
> 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,
>
>
Make sure that initdb is the version you want
   initdb --version

then
   initdb -E UTF8 -D /var/lib/pgsql/data

then post the output of that.

kllint.

--
Klint Gore
Database Manager
Sheep CRC
A.G.B.U.
University of New England
Armidale NSW 2350

Ph: 02 6773 3789
Fax: 02 6773 3266
EMail: kgore4@une.edu.au


pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: Need Help Recovering from Botched Upgrade Attempt
Next
From: Tom Lane
Date:
Subject: Re: postgres-devel for 8.3.3