Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 54C299FB28D for ; Tue, 14 Nov 2006 18:50:50 -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 55777-03 for ; Tue, 14 Nov 2006 18:50:47 -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 525C49FA5C8 for ; Tue, 14 Nov 2006 18:50:47 -0400 (AST) Received: from adsl-69-226-255-19.dsl.pltn13.pacbell.net ([69.226.255.19]:59653 helo=discord.home.frostconsultingllc.com) by glacier.frostconsultingllc.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1Gk76y-0001bE-91; Tue, 14 Nov 2006 14:50:43 -0800 Received: from localhost (localhost.localdomain [127.0.0.1]) by discord.home.frostconsultingllc.com (8.13.7/8.13.7) with ESMTP id kAEMoZFi028130; Tue, 14 Nov 2006 14:50:35 -0800 Date: Tue, 14 Nov 2006 14:50:35 -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: <200611142243.kAEMhZf02180@momjian.us> Message-ID: References: <200611142243.kAEMhZf02180@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/18 X-Sequence-Number: 3852 On Tue, 14 Nov 2006, Bruce Momjian wrote: >> 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. >> >> I guess it's kind of a fine line how it gets defined? > > Hmmm. Interesting. Does anyone else have details or an opinion on > this? The fact that there is something sitting above the servers seems > to be the defining issue of calling it query broadcast. My thinking on the definition of clustering was that there is some smarts for graceful failover and automated or semi-automated ways of bringing failed DB servers back up to date and online with the rest of the servers in the cluster. All servers need to be able to accept writes, but do we differentiate on where the writes originated (i.e. middleware or another postgresql server) or on functionality? -- Jeff Frost, Owner Frost Consulting, LLC http://www.frostconsultingllc.com/ Phone: 650-780-7908 FAX: 650-649-1954