From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
Cc: | Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: RPMS for 7.3 beta. |
Date: | 2002-09-18 02:53:41 |
Message-ID: | 200209180253.g8I2rfc05679@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Christopher Kings-Lynne wrote:
> > I just want people to not get bit in a bad way and decide they
> > don't want to
> > use PostgreSQL after all. And with the new features of 7.3, lots
> > of users
> > who might have begun with 7.2 are going to want to upgrade -- but
> > if it's too
> > painful.... Sorry, it's just a sore spot for me, this whole
> > upgrade issue.
> > I know Oliver has the same problem, with slightly different presentation.
>
> IS there any solution to Postgres's upgrade problems? I mean, ever? With
> the complex catalog design, etc - how is it every possible for us to do a
> plug-n-play major version upgrade (assuming datafile format doesn't change
> anymore)
>
> How does pg_upgrade work?
pg_upgrade sort of worked for 7.2 but I got to it too late and I didn't
properly expand the pg_clog files. In 7.3, the file format has changed.
If we don't change the format for 7.4, I can do it, but I have to add
schema stuff to it. Shouldn't be too hard.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2002-09-18 03:04:02 | Re: RPMS for 7.3 beta. |
Previous Message | Christopher Kings-Lynne | 2002-09-18 02:27:10 | Re: RPMS for 7.3 beta. |