Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 06B359FB25A for ; Tue, 14 Nov 2006 18:02:44 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 80813-05 for ; Tue, 14 Nov 2006 22:02:36 +0000 (UTC) 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 BE8D59FB232 for ; Tue, 14 Nov 2006 18:02:35 -0400 (AST) Received: from adsl-69-226-255-19.dsl.pltn13.pacbell.net ([69.226.255.19]:42966 helo=discord.home.frostconsultingllc.com) by glacier.frostconsultingllc.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1Gk6MK-0001Qo-Ln; Tue, 14 Nov 2006 14:02:31 -0800 Received: from localhost (localhost.localdomain [127.0.0.1]) by discord.home.frostconsultingllc.com (8.13.7/8.13.7) with ESMTP id kAEM2Lfb020441; Tue, 14 Nov 2006 14:02:21 -0800 Date: Tue, 14 Nov 2006 14:02:21 -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: <200611142142.kAELgNO25509@momjian.us> Message-ID: References: <200611142142.kAELgNO25509@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/12 X-Sequence-Number: 3846 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. -- Jeff Frost, Owner Frost Consulting, LLC http://www.frostconsultingllc.com/ Phone: 650-780-7908 FAX: 650-649-1954