Re: Release cycle length - Mailing list pgsql-hackers

From Jim C. Nasby
Subject Re: Release cycle length
Date
Msg-id 20031125050844.GC67015@nasby.net
Whole thread Raw
In response to Re: Release cycle length  (Jan Wieck <JanWieck@Yahoo.com>)
Responses Re: Release cycle length
List pgsql-hackers
On Fri, Nov 21, 2003 at 01:32:38PM -0500, Jan Wieck wrote:
> bootstrap mode to apply the changes, could be an idea to think of. It 
> would still require some downtime, but nobody can avoid that when 
> replacing the postgres binaries anyway, so that's not a real issue. As 
> long as it eliminates dump, initdb, reload it will be acceptable.
Has anyone looked at using replication as a migration method? If
replication can be setup in such a way that you can replicate from an
old version to a new version, you can use that to build the new version
of the database on a seperate machine/instance while the old version is
still live. With some sophisticated middleware, you could theoretically
migrate without any downtime.
-- 
Jim C. Nasby, Database Consultant                  jim@nasby.net
Member: Triangle Fraternity, Sports Car Club of America
Give your computer some brain candy! www.distributed.net Team #1828

Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"


pgsql-hackers by date:

Previous
From: Christopher Kings-Lynne
Date:
Subject: Re: Build farm
Next
From: Tom Lane
Date:
Subject: Re: [7.4] statistics collector: Protocol not supported