X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id CB9F4D1D9E9 for ; Tue, 25 Nov 2003 05:09:16 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 38823-08 for ; Tue, 25 Nov 2003 01:08:46 -0400 (AST) Received: from flake.decibel.org (flake.decibel.org [66.143.173.58]) by svr1.postgresql.org (Postfix) with SMTP id 8305DD1D8FC for ; Tue, 25 Nov 2003 01:08:45 -0400 (AST) Received: (qmail 90850 invoked by uid 1001); 25 Nov 2003 05:08:44 -0000 Date: Mon, 24 Nov 2003 23:08:44 -0600 From: "Jim C. Nasby" To: Jan Wieck Cc: Alvaro Herrera , Christopher Kings-Lynne , Tom Lane , Peter Eisentraut , PostgreSQL Development Subject: Re: Release cycle length Message-ID: <20031125050844.GC67015@nasby.net> References: <20031117202346.M731@ganymede.hub.org> <3FBB7F20.8050005@Yahoo.com> <6400.1069359578@sss.pgh.pa.us> <3FBD6CAA.7040500@familyhealth.com.au> <20031121130359.GE26392@dcc.uchile.cl> <3FBE5A46.4090102@Yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3FBE5A46.4090102@Yahoo.com> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.9-RELEASE i386 X-Distributed: Join the Effort! http://www.distributed.net X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200311/1311 X-Sequence-Number: 47599 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?"