Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 483F59FB26E for ; Tue, 14 Nov 2006 18:18:39 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 47982-03 for ; Tue, 14 Nov 2006 18:18:32 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from glacier.frostconsultingllc.com (glacier.frostconsultingllc.com [64.127.99.90]) by postgresql.org (Postfix) with ESMTP id CFC9D9FB25A for ; Tue, 14 Nov 2006 18:18:28 -0400 (AST) Received: from adsl-69-226-255-19.dsl.pltn13.pacbell.net ([69.226.255.19]:46835 helo=discord.home.frostconsultingllc.com) by glacier.frostconsultingllc.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1Gk6bk-0001TP-Pu; Tue, 14 Nov 2006 14:18:27 -0800 Received: from localhost (localhost.localdomain [127.0.0.1]) by discord.home.frostconsultingllc.com (8.13.7/8.13.7) with ESMTP id kAEMIKAo021062; Tue, 14 Nov 2006 14:18:20 -0800 Date: Tue, 14 Nov 2006 14:18:20 -0800 (PST) From: Jeff Frost X-X-Sender: jeff@discord.home.frostconsultingllc.com To: Bruce Momjian cc: Chris Browne , pgsql-docs@postgresql.org In-Reply-To: <200611142204.kAEM4Ba27328@momjian.us> Message-ID: References: <200611142204.kAEM4Ba27328@momjian.us> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-SA-Exim-Connect-IP: 69.226.255.19 X-SA-Exim-Mail-From: jeff@glacier.frostconsultingllc.com Subject: Re: [HACKERS] Replication documentation addition X-SA-Exim-Version: 4.2 (built Tue, 02 May 2006 07:39:18 -0400) X-SA-Exim-Scanned: Yes (on glacier.frostconsultingllc.com) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200611/14 X-Sequence-Number: 3848 On Tue, 14 Nov 2006, Bruce Momjian wrote: > Jeff Frost wrote: >> On Tue, 14 Nov 2006, Bruce Momjian wrote: >> >>> Your description was too detailed, but I took some of your concepts: >>> >>> >>> In clustering, each server can accept write requests, and these >>> write requests are broadcast from the original server to all >>> other servers before each transaction commits. Heavy write >>> activity can cause excessive locking, leading to poor performance. >>> In fact, write performance is often worse than that of a single >>> server. Read requests can be sent to any server. Clustering >>> is best for mostly read workloads, though its big advantage is >>> that any server can accept write requests --- there is no need >>> to partition workloads between read/write and read-only servers. >>> >>> >>> >>> Clustering is implemented by Oracle in their >>> RAC product. PostgreSQL >>> does not offer this type of load balancing, though >>> PostgreSQL two-phase commit (>> linkend="sql-prepare-transaction-title"> and >> "sql-commit-prepared-title">) can be used to implement this in >>> application code or middleware. >>> >> >> Bruce, >> >> Continuent's uni/cluster middleware product implements this type of >> clustering/load balancing. Perhaps it warrants a mention? Not sure how far >> we want to get into listing external products. > > We had a long discussion about that and felt that recommending > commercial products or even every open source project was too much. The > idea was that we should reference a web page that has them all mentioned, > but no one has set one up yet. That makes sense, I just hate to see us say something like "Oracle can do this with RAC but PostgreSQL cannot." -- Jeff Frost, Owner Frost Consulting, LLC http://www.frostconsultingllc.com/ Phone: 650-780-7908 FAX: 650-649-1954