Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 621BD9FB20F; Tue, 24 Oct 2006 16:23:33 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 27439-02; Tue, 24 Oct 2006 19:23:10 +0000 (UTC) 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 E2AE89FB1E4; Tue, 24 Oct 2006 16:23:08 -0300 (ADT) Received: from [192.168.77.26] (p54BDC8CB.dip0.t-ipconnect.de [::ffff:84.189.200.203]) (AUTH: CRAM-MD5 markus@bluegap.ch) by bugaboo.mu with esmtp; Tue, 24 Oct 2006 21:23:06 +0200 id 004223A0.453E681B.0000091A Message-ID: <453E681A.3000004@bluegap.ch> Date: Tue, 24 Oct 2006 21:23:06 +0200 From: Markus Schiltknecht User-Agent: Thunderbird 1.5.0.7 (X11/20060927) MIME-Version: 1.0 To: josh@agliodbs.com CC: pgsql-hackers@postgresql.org, Bruce Momjian , PostgreSQL-documentation Subject: Re: [HACKERS] Replication documentation addition References: <200610240339.k9O3dYh19144@momjian.us> <200610241137.47486.josh@agliodbs.com> In-Reply-To: <200610241137.47486.josh@agliodbs.com> 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=0.855 tagged_above=0 required=5 tests=FORGED_RCVD_HELO, SARE_SPEC_REPLICA X-Spam-Level: X-Archive-Number: 200610/49 X-Sequence-Number: 3770 Hello Josh, Josh Berkus wrote: > Hmmm ... while the primer on different types of replication is fine, I > think what users were really looking for is a listing of the different > replication solutions which are available for PostgreSQL and how to get > them. Well, let's see what we have: * Shared Disk Fail Over * Warm Standby Using Point-In-Time Recovery * Point-In-Time Recovery these first three require quite some configuration, AFAIK there is no tool or single solution you can download, install and be happy with. I probably wouldn't even call them 'replication solutions'. For me those are more like backups with fail-over capability. * Continuously Running Fail-Over Server (BTW, what is 'partial replication' supposed to mean here?) Here we could link to Slony. * Data Partitioning Here we can't provide a link, it's just a way to handle the problem in the application code. * Query Broadcast Replication Here we could link to PgPool. * Multi-Master Replication (or better: Distributed Shared Memory Replication) No existing solution for PostgreSQL. Looking at that, I'm a) missing PgCluster and b) arguing that we have to admit that we simply can not 'list .. replication solutions ... and how to get them' because all of the solutions mentioned need quite some knowledge and require a more or less complex installation and configuration. Regards Markus