X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 7CE173A5821 for ; Tue, 25 Jan 2005 21:50:14 +0000 (GMT) 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 24045-01 for ; Tue, 25 Jan 2005 21:50:09 +0000 (GMT) Received: from floppy.pyrenet.fr (news.pyrenet.fr [194.250.190.2]) by svr1.postgresql.org (Postfix) with ESMTP id 9732B3A5806 for ; Tue, 25 Jan 2005 21:50:10 +0000 (GMT) Received: by floppy.pyrenet.fr (Postfix, from userid 106) id 351C8319CE; Tue, 25 Jan 2005 22:50:10 +0100 (MET) From: Christopher Browne X-Newsgroups: pgsql.performance Subject: Re: PostgreSQL vs. Oracle vs. Microsoft Date: Tue, 25 Jan 2005 16:46:48 -0500 Organization: cbbrowne Computing Inc Lines: 25 Message-ID: References: <20050109180452.03723387.frank@wiles.org> <41EFF265.40902@cheapcomplexdevices.com> <12826.1106290803@sss.pgh.pa.us> <20050125175920.GA3392@gp.word-to-the-wise.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@news.hub.org X-message-flag: Outlook is rather hackable, isn't it? X-Home-Page: http://www.cbbrowne.com/info/ X-Affero: http://svcs.affero.net/rm.php?r=cbbrowne User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4 (Corporate Culture, linux) Cancel-Lock: sha1:2bGeMEejh249i4No2o43696gP2g= To: pgsql-performance@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.081 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200501/486 X-Sequence-Number: 10176 Centuries ago, Nostradamus foresaw when steve@blighty.com (Steve Atkins) would write: > As a bit of obPostgresql, though... While the registry for .org is > run on Postgresql, the actual DNS is run on Oracle. That choice was > driven by the availability of multi-master replication. > > Like many of the cases where the problem looks like it needs > multi-master replication, though, it doesn't really need it. A > single master at any one time, but with the ability to dub any of > the slaves a new master at any time would be adequate. If that were > available for Postgresql I'd choose it over Oracle were I doing a > big distributed database backed system again. Well, this is something that actually _IS_ available for PostgreSQL in the form of Slony-I. Between "MOVE SET" (that does controlled takeover) and "FAILOVER" (that recovers from the situation where a 'master' node craters), this has indeed become available. Automating activation of the failover process isn't quite there yet, though that's mostly a matter that the methodology would involve considerable tuning of recovery scripts to system behaviour. -- select 'cbbrowne' || '@' || 'ntlug.org'; http://cbbrowne.com/info/slony.html Pay no attention to the PDP-11 behind the front panel. -- PGS, in reference to OZ