>Get a second machine, set it up to be as identical to the existing machine as you can - aside from it not >being near
death- and migrate "production" to it.
>
>Then on the machine described above install v10 and whatever else you need for staging/testing and then >once
everythingchecks out migrate the production database to the new machine and point production >resources to it.
>
>Lastly, but first, consider finding an experienced professional to evaluate you exact current >circumstances and
executethe above - or whatever they recommend. The first item warrants doing that at >the least. You can delay
decidingon how to approach the second option until after your production >environment is stable.
>
>David J.
Thanks for that. It's effectively what I've done by re-incarnating a disused dev server that had an identical install
asthe prod db server. I dumped the db's last night and loaded them up without any issue. It's a slower machine but it
hasn'tgot disks that are going AWOL and at least gives me some breathing space to setup the new server and test migrate
thedatabases across to a newer version of PostgreSQL today/over the weekend.
