X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 1BAD7D1B430 for ; Wed, 21 Jul 2004 00:15:49 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 72477-02 for ; Wed, 21 Jul 2004 03:15:43 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id 5E119D1B38F for ; Wed, 21 Jul 2004 00:15:43 -0300 (ADT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.12.9/8.12.9) with ESMTP id i6L3FRr1068237 for ; Wed, 21 Jul 2004 03:15:42 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id i6L2lLsw058673 for pgsql-admin@postgresql.org; Wed, 21 Jul 2004 02:47:21 GMT From: Gaetano Mendola X-Newsgroups: comp.databases.postgresql.admin Subject: Re: Replication in main PostgreSQL codebase Date: Sat, 17 Jul 2004 12:07:11 +0200 Organization: PYRENET Midi-pyrenees Provider Lines: 34 Message-ID: <40F8FA4F.2060808@bigfoot.com> References: <20040706170510.W71486@ganymede.hub.org> <200407062029.i66KTpt22440@candle.pha.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@pyrenet.fr To: Bruce Momjian User-Agent: Mozilla Thunderbird 0.7.1 (Windows/20040626) X-Accept-Language: en-us, en In-Reply-To: <200407062029.i66KTpt22440@candle.pha.pa.us> X-Enigmail-Version: 0.84.2.0 X-Enigmail-Supports: pgp-inline, pgp-mime To: pgsql-admin@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200407/230 X-Sequence-Number: 14298 Bruce Momjian wrote: > OK, I reworded the replication TODO section and moved it under > Administration: > > * Improve replication solutions > o Automatic failover The Automatic failover is already available, we use the RH cluster solution and it works really well, we never had a failure till now but all the our simulations ( power off, hardware failure ) are working well. We have almost 3 year of 24/24 7/7 without macro interruption, only fews minutes during the 7.0 -> 7.1 -> ... -> 7.4 upgrades. With the RH solution we are also able to perform the minor upgrades ( 7.4.1 -> 7.4.2 for example ) without one single minute of interruption: 1) Upgrade on passive node 2) Relocation service 3) Upgrade on the active node 4) Relocation service it would be great from this point of view if the pg_upgrade could handle also the major version upgrade without need to dump, init, reload the db. Regards Gaetano Mendola