Re: Need Help Recovering from Botched Upgrade Attempt

From: Adrian Klaver <aklaver(at)comcast(dot)net>
To: pgsql-general(at)postgresql(dot)org
Cc: Rich Shepard <rshepard(at)appl-ecosys(dot)com>
Subject: Re: Need Help Recovering from Botched Upgrade Attempt
Date: 2008-06-18 02:37:05
Message-ID: 200806171937.05524.aklaver@comcast.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tuesday 17 June 2008 7:18 pm, 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!

Define nothing. When you ran initdb there where no messages? Also when in
doubt I use the full path /var/lib/pgsql/bin/initdb as you have an old
version of initdb present in the old version directory you copied. When you
have two versions present at the same time it is easy to get cross reference
problems.

>
> 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

--
Adrian Klaver
aklaver(at)comcast(dot)net

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2008-06-18 03:11:27 Re: postgres-devel for 8.3.3
Previous Message Klint Gore 2008-06-18 02:36:25 Re: Need Help Recovering from Botched Upgrade Attempt