Jim Mercer wrote:
>
> On Fri, Mar 24, 2000 at 02:26:44PM -0400, The Hermit Hacker wrote:
> > Since there has been very little bug reports between beta2 and beta3, this
> > one is considered to be the first Candidate for Release. Altho its still
> > beta, there should be negligible risk of a subsequence "beta requiring an
> > initdb" happening ...
> is 7.0 going to require a dump and restore of the entire database?
> i've got some multi-gig databases that would make that a pain in the ass.
It is standard operating procedure for PostgreSQL to have to do a
dump/upgrade/initdb/restore cycle every major version increment -- and
has been for many moons. It certainly is a pain -- but, IMHO, it could
be a worse pain. Granted, it could be made more transparent, but noone
has done this as of yet.
IMHO, again, it is better to _know for a fact_ that a dump/reload is
going to be required _every_ major version upgrade than to have
surprises -- and to have to use a db that has been coded around
backwards compatibility.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
