On 02/13/2016 12:43 PM, Mick wrote: > > Thank you Michael. It was pretty painless TBH, almost as easy as upgrading > mysql. ;-) Your page also nicely details the alternative, which I did not > try out. >
I wrote that when postgresql-9.0 was released and was the first version that had pg_upgrade. It sounds great at first... I guess it feels dangerous to dump/restore your entire database cluster to a text file (even though I've never had a problem doing it). But, I kept running into problems, even following my own instructions step-by-step. For example, pg_upgrade will refuse to upgrade clusters with different encodings. A dump/restore works just fine there. Plus, it became annoying to have to follow a list every time I needed to do an upgrade (I have more than one postgres server). The pg_upgrade route is extremely sensitive to the order in which you do things. Meanwhile, the dump/restore route I know off the top of my head: 1. make sure the new version works 2. dump everything 3. switch to the new version 4. load the dump There are details at each step, but the order can be fudged and it's easy to fix if you forget something. As long as there are no known problems with the dump/restore method, I don't see any reason to bother with the "new" way.
