Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 811459FB2E9; Wed, 25 Oct 2006 12:43:58 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 86381-05; Wed, 25 Oct 2006 12:43:52 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- Received: from bugaboo.mu (ns1.bugaboo.mu [213.133.111.57]) by postgresql.org (Postfix) with ESMTP id 5FFEB9FB2C9; Wed, 25 Oct 2006 12:43:52 -0300 (ADT) Received: from [192.168.77.26] (p54BDC1DC.dip0.t-ipconnect.de [::ffff:84.189.193.220]) (AUTH: CRAM-MD5 markus@bluegap.ch) by bugaboo.mu with esmtp; Wed, 25 Oct 2006 17:43:50 +0200 id 021CACF7.453F8636.00007AD1 Message-ID: <453F8636.2070906@bluegap.ch> Date: Wed, 25 Oct 2006 17:43:50 +0200 From: Markus Schiltknecht User-Agent: Thunderbird 1.5.0.7 (X11/20060927) MIME-Version: 1.0 To: "Jim C. Nasby" CC: Bruce Momjian , Hannu Krosing , PostgreSQL-documentation , PostgreSQL-development Subject: Re: [HACKERS] Replication documentation addition References: <200610250255.k9P2tRM09844@momjian.us> <453F3083.6080302@bluegap.ch> <20061025135740.GH26892@nasby.net> In-Reply-To: <20061025135740.GH26892@nasby.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=1.03 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO, SARE_SPEC_REPLICA X-Spam-Level: * X-Archive-Number: 200610/90 X-Sequence-Number: 3811 Hi, Jim C. Nasby wrote: > Those to statements are at odds with each other, at least based on > everyone I've ever talked to in a commercial setting. People will use > terms like 'replication', 'HA' or 'clustering' fairly interchangably. > Usually what these folks want is some kind of high-availability > solution. A few are more concerned with scalability. Sometimes it's a > combination of both. That's why I think it's good for the chapter to > deal with both aspects of this. Yabut... at least the PostgreSQL manual should uses the terms correctly. And while I do perfectly agree that it's a fail-over solution and it should be mentioned in that section, I'm arguing that it's not replication. Regards Markus