"Steve Wolfe" <nw@codon.com> wrote:
> I had an older installation of postgresql, 7.1.3. I got down the
packages for
> 7.3.2. I looked at a few of the files in the directories where the
packages
> were kept, and seeing no particular warnings, I ran rpm -Uvh
postgresql*,
> which ran without a hitch, until I restarted the postmaster. Then it
informed
> me that I should have dumped the damned database before I upgraded the
> binaries.
>
> This is like seeing the "Bridge Out" sign at the bottom of the river.
>
> Why didn't the preinstall scripts dump the database? Why doesn't the FAQ
or
> the README in the download directory mention the required procedure?
I'm in the same boat. The thread that followed went off into the merits of
rpms and building from source ... always fun, but not what I need right
now. My question is, how do I recover? I have a bunch of really nice data
sitting in a database I can no longer access. Is there a conversion
procedure? Do I build the previous version? How do I do that?
I am running FreeBSD 4.6.2 and installed from the ports collection using
portupgrade. The "problem" with portupgrade in this situation is that it
fully automates the build and install process. Even if the "make" command
warned about the need to dump data (and maybe it did) there was no chance
to do anything before "make install." From now on I'll exclude postgresql
from the portupgrade procedure.
Except for this one glitch I have been very happy with postgresql. Live
and learn!
--
_/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/
_/ _/
_/ Gary Dunn _/
_/ Open Slate Project _/
_/ http://openslate.sourceforge.net/ _/
_/ http://www.aloha.com/~knowtree/ _/
_/ Honolulu _/
_/ registered Linux user #273809 _/
_/ _/
_/ This tagline is umop apisdn. _/
_/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/