Received: from localhost (uranus.hub.org [200.46.204.60]) by postgresql.org (Postfix) with ESMTP id B17A59FA4B4 for ; Tue, 14 Nov 2006 20:11:49 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.60]) (amavisd-new, port 10024) with ESMTP id 59204-06 for ; Tue, 14 Nov 2006 20:11:48 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from momjian.us (momjian.us [70.90.9.53]) by postgresql.org (Postfix) with ESMTP id 87C209FA497 for ; Tue, 14 Nov 2006 20:11:48 -0400 (AST) Received: (from bruce@localhost) by momjian.us (8.11.6/8.11.6) id kAF0Beb21787; Tue, 14 Nov 2006 19:11:40 -0500 (EST) From: Bruce Momjian Message-Id: <200611150011.kAF0Beb21787@momjian.us> Subject: Re: [HACKERS] Replication documentation addition In-Reply-To: To: Jeff Frost Date: Tue, 14 Nov 2006 19:11:39 -0500 (EST) CC: Chris Browne , pgsql-docs@postgresql.org X-Mailer: ELM [version 2.4ME+ PL123] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200611/21 X-Sequence-Number: 3855 Jeff Frost wrote: > On Tue, 14 Nov 2006, Bruce Momjian wrote: > > >> 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 > > > > No, even replication servers can have that. > > > >> differentiate on where the writes originated (i.e. middleware or another > >> postgresql server) or on functionality? > > > > Fundamentally, broadcast means the queries are being propogated outside > > the server, with the benefits and limitations inherent in that. > > I'd definitely have to agree with you on that. I guess I'm trying to decide > what differentiates clustering for load balancing from query broadcast based > on your text. Maybe just don't use the word broadcast here: > > "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." > > Unfortunately, I can't seem to come up with anything more clever. Basically, when you are broadcasting outside the server, you are broadcasting SQL queries, and those queries do not have information about non-deterministic functions and have issues with universal commits on all node. I think I now see your point about using the word "broadcast" for both clustering and middle-ware broadcast. Let me find some new wording and repost. -- Bruce Momjian bruce@momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +