From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Jim Mercer <jim(at)reptiles(dot)org> |
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:18:15 |
Message-ID: | 200010161618.MAA10088@candle.pha.pa.us |
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.
I see. Hmmm.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Marcin Mazurek | 2000-10-16 16:20:03 | plpgsql, insert with wariables in function triggered |
Previous Message | bmccoy | 2000-10-16 16:13:37 | Re: (redefinition) alter table, add foreign key constraint |