On Monday 10 Nov 2014 13:16:25 cov...@ccs.covici.com wrote: > Michael Orlitzky <m...@gentoo.org> wrote: > > On 11/10/2014 06:04 AM, cov...@ccs.covici.com wrote: > > > Hi. I have a puzzle regarding upgrading postgresql. In my recent > > > world update I went from 9.4_beta2 to beta3, but when I tried to start > > > the server, it complained that the databases were written with a > > > different "catalog version" -- whatever that is, and the pg_upgrade > > > tool requires both old and new binaries to actually upgrade the > > > database. So as a temporary measure, I went back to beta2 and things > > > worked again. So what the heck are you supposed to do here, I like > > > pg, but this is very strange to me. > > > > > > Thanks in advance for any suggestions. > > > > pg_upgrade has always been a PITA for me. There's an easier way that > > always works: run pg_dumpall, upgrade postgres, and then restore the > > dump file. > > > > If your databases are small enough, it's much less stressful, and it > > works for major version bumps as well. > > > > If you're worried about overwriting your data, you could always back up > > the beta2 binary files, and then create empty databases under beta3 > > before restoring. > > Thanks, maybe I will do that next time.
You may also want to file a bug? There may be need for a elog pre-emerge message or some such for users to know how to deal with this in a gentoo system without tearing their hair out. -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
