> Tom Lane 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.
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
