Re: 7.1 Release Date

From: Jim Mercer <jim(at)reptiles(dot)org>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Trond Eivind Glomsrød <teg(at)redhat(dot)com>, The Hermit Hacker <scrappy(at)hub(dot)org>, pgsql-general(at)postgresql(dot)org
Subject: Re: 7.1 Release Date
Date: 2000-10-16 16:12:36
Message-ID: 20001016121236.F15903@reptiles.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Oct 16, 2000 at 12:00:59PM -0400, Bruce Momjian wrote:
> > > Migration tools might ease the pain, sure (though I'd still recommend
> > > doing a full backup before a major version upgrade, just on safety
> > > grounds; so the savings afforded by a tool might not be all that much).
> >
> > What is needed, IMHO, is a replacement to the pg_upgrade script that can
> > do the following:
> > 1.) Read _any_ previous version's format data files;
> > 2.) Write the current version's data files (without a running
> > postmaster).
>
> Let me ask. Could people who need to be up all the time dump their
> data, install PostgreSQL on another machine, load that in, then quickly
> copy the new version to the live machine and restart. Seems like
> downtime would be minimal.

sure, i've only got 25+ gig of tables, two of which are 10+ gig each.

8^(

it certainly would be nice to have a quicker process than dump/reload.

--
[ Jim Mercer jim(at)reptiles(dot)org +1 416 410-5633 ]
[ Reptilian Research -- Longer Life through Colder Blood ]
[ Don't be fooled by cheap Finnish imitations; BSD is the One True Code. ]

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message bmccoy 2000-10-16 16:13:37 Re: (redefinition) alter table, add foreign key constraint
Previous Message Bruce Momjian 2000-10-16 16:10:33 Re: Ignore when using COPY FROM