Hacksaw,
I feel your pain but can't share your experience.
The FreeBSD port of PostgreSQL says in nice big (err, monospaced) letters:
YOU SHOULD BACKUP YOUR DATA BEFORE PROCEEDING!
I'm pretty sure the normal (compile, install) instructions will let you know to back things up.
Yet another example of why RPMs are evil?
--------------------------
David Olbersen
iGuard Engineer
11415 West Bernardo Court
San Diego, CA 92127
1-858-676-2277 x2152
> -----Original Message-----
> From: Hacksaw [mailto:hacksaw@hacksaw.org]
> Sent: Thursday, March 27, 2003 10:17 AM
> To: pgsql-admin@postgresql.org
> Subject: [ADMIN] Upgrading: So now you tell me!!?!?
>
>
> 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?
>
> If there is going to be a conflict that might require having
> the old binaries
> around, why do the new ones replace the old ones?
> --
> In the creative leap, history waits outside.
> http://www.hacksaw.org -- http://www.privatecircus.com -- KB1FVD
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>
