Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id B20B664FC4F for ; Wed, 26 Nov 2008 00:15:41 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 34328-09 for ; Wed, 26 Nov 2008 00:15:23 -0400 (AST) X-Greylist: delayed 00:19:58.731626 by SQLgrey-1.7.6 Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.174]) by mail.postgresql.org (Postfix) with ESMTP id 628A464FC04 for ; Wed, 26 Nov 2008 00:15:16 -0400 (AST) Received: by ug-out-1314.google.com with SMTP id k40so1280053ugc.7 for ; Tue, 25 Nov 2008 20:15:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=WVKjncQmELBdbff2YA52xHN/c0VM0E/UVY9PYzIDbmY=; b=qgegt93LE9c3pTbeT+PxSgFGAud7xoT1bWG41BqYEgKuCqH2FHjS2bLtBk0lmhfiZX /sZ5ZpfDQkg2fnvZ0yWauRcoV/QDrBSAONA7ZEi2cx7gV7p/O78SlQilD2nd7vXhAf9z epfiJd5ioru7J10rpiN3cf2LyU0Wrnx3ARki8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=JsE14bQa6Ex+D67bBPUtUMqHmb/eVYc4BkwMPm2+ocfDzDXn9CAsVqGXy3ad1VV7f9 l6MeZwN18lUMp/AFqzavQznVmWEiIgLUtXjxDKjddLmPaPvSmdemsST2GuKLD9VUUoTS yLSuOcoeH06iqsgvJsGeqTRbtaVzQSNdQR6m8= Received: by 10.103.241.5 with SMTP id t5mr1911431mur.127.1227671281510; Tue, 25 Nov 2008 19:48:01 -0800 (PST) Received: by 10.103.178.19 with HTTP; Tue, 25 Nov 2008 19:48:01 -0800 (PST) Message-ID: Date: Wed, 26 Nov 2008 14:48:01 +1100 From: "Jamie Tufnell" To: pgsql-admin@postgresql.org Subject: Best option for expanding beyond 1 pg server in this situation MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200811/145 X-Sequence-Number: 30799 Hi, We have been wanting to HA our pgsql server for some time now. We're actually reaching the limits of our current server now, so there is a pressing need to do something to ease the load too. There are several individual solutions to both of these problems. I was hoping I could get some advice from someone more experienced though, about what the simplest most effective way of moving forward would be? Hopefully I can squash both HA and LB with the same solution. So far I've narrowed it down to Slony-I master/slave replication with failover or pgpool-II with heartbeat for failover. The pgpool-II configuration matrix (http://pgpool.projects.postgresql.org/) isn't terribly clear (there's no legend) but it leads me to believe failover and load balancing are mutually exclusive options. Is that so? About our environment: PostgreSQL 8.3. Over 90% reads. Low data turnover on all tables involved in most of those reads. High data turnover on a select few tables. Overall database size is quite small (1GB). Any advice/help much appreciated. Jamie