Most OS people screw things up between major revisions.
From watching friends and also this list, the lesson is just what you stated:
Do a full system backup before any major revision changes in any software
whatsoever. It's saved my but once. I lost the entire registry in windows95
once. Fortunately, after doing a file compare, I found that was the only file
corrupted, and restored a 3 month old one. I had to reinstall a few programs and
delete the registry entries for some that were no longer resident. But it was
better than reinstalling EVERYTHING, including OS patches.
At the current moment, I keep a full harddrive backup of the harddrives in my
box on older machines. What to do with WinXP, i don't know yet. In fact, I don't
know how to do a drive copy with Linux either. something else to learn, I guess.
Guy Fraser wrote:
> Bob Kline wrote:
>
>> On Sat, 12 Apr 2003, Lamar Owen wrote:
>>
>> [ Very throrough and thoughtful reply, ending ...]
>>
>>
>>
>>> So, unless some things change at fundamental levels, it's going to
>>> remain a problem. The lesson is to always do an ASCII dump before an
>>> OS upgrade. PostgreSQL is not the only program that can be borked in
>>> an OS upgrade, either
>>>
> What a mess...
> RH has fouled up a lot of stuff lately...
> I'm not even going to go there...
> :-(
>
>> Thanks very much for your excellent reply, and for your efforts to make
>> things better. I've learned my lesson for the future. I hope these
>> problems won't drive away too many prospective PostgreSQL users.
>>
>>
>>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>
