1 |
On Monday 10 Nov 2014 13:16:25 covici@××××××××××.com wrote: |
2 |
> Michael Orlitzky <mjo@g.o> wrote: |
3 |
> > On 11/10/2014 06:04 AM, covici@××××××××××.com wrote: |
4 |
> > > Hi. I have a puzzle regarding upgrading postgresql. In my recent |
5 |
> > > world update I went from 9.4_beta2 to beta3, but when I tried to start |
6 |
> > > the server, it complained that the databases were written with a |
7 |
> > > different "catalog version" -- whatever that is, and the pg_upgrade |
8 |
> > > tool requires both old and new binaries to actually upgrade the |
9 |
> > > database. So as a temporary measure, I went back to beta2 and things |
10 |
> > > worked again. So what the heck are you supposed to do here, I like |
11 |
> > > pg, but this is very strange to me. |
12 |
> > > |
13 |
> > > Thanks in advance for any suggestions. |
14 |
> > |
15 |
> > pg_upgrade has always been a PITA for me. There's an easier way that |
16 |
> > always works: run pg_dumpall, upgrade postgres, and then restore the |
17 |
> > dump file. |
18 |
> > |
19 |
> > If your databases are small enough, it's much less stressful, and it |
20 |
> > works for major version bumps as well. |
21 |
> > |
22 |
> > If you're worried about overwriting your data, you could always back up |
23 |
> > the beta2 binary files, and then create empty databases under beta3 |
24 |
> > before restoring. |
25 |
> |
26 |
> Thanks, maybe I will do that next time. |
27 |
|
28 |
You may also want to file a bug? There may be need for a elog pre-emerge |
29 |
message or some such for users to know how to deal with this in a gentoo |
30 |
system without tearing their hair out. |
31 |
|
32 |
-- |
33 |
Regards, |
34 |
Mick |