From: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
---|---|
To: | Karl DeBisschop <kdebisschop(at)range(dot)infoplease(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, karl(at)debisschop(dot)net, "J(dot) Atwood" <jatwood(at)bwanazulia(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: 7.0 RPM? |
Date: | 2000-05-10 13:39:35 |
Message-ID: | 39196697.20EFF03C@alumni.caltech.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
> > 7.0RC5 is database-compatible with the final, earlier betas are *not*.
> > You can use pg_upgrade to update from any 6.5-or-later version if you
> > are feeling adventurous, but I'd definitely suggest making a backup
> > first in case things go wrong and you have to initdb and restore.
> Sorry if I was not clear. The RPMs I prepared use Lamar Owen spec from RC1,
> but use final release sources. Upgrading from final release to final release
> should not be a problem, I think. I only recommended it because I understand
> from his recent posts sthat Lamar has many inprovements to the RPM install
> script that I have not taken advantage of.
Tom's point is that RC5 is *not* database-compatible with previous
release candidates due to a last minute bug fix in the location of
group table indices.
So anything earlier than RC5 needs (at least) a pg_upgrade, and (for
me) preferably a full dump/initdb/restore cycle.
- Thomas
--
Thomas Lockhart lockhart(at)alumni(dot)caltech(dot)edu
South Pasadena, California
From | Date | Subject | |
---|---|---|---|
Next Message | Ned Lilly | 2000-05-10 14:11:22 | Re: Steering committee responce to Great Bridge LLC |
Previous Message | Karl DeBisschop | 2000-05-10 13:21:12 | Re: 7.0 RPM? |
From | Date | Subject | |
---|---|---|---|
Next Message | The Hermit Hacker | 2000-05-10 13:41:31 | pg_hba.conf && ident ... |
Previous Message | Karl DeBisschop | 2000-05-10 13:21:12 | Re: 7.0 RPM? |