Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 17CE46501FC for ; Wed, 26 Nov 2008 04:39:11 -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 85917-08 for ; Wed, 26 Nov 2008 04:39:08 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from zimbra.linuxsilo.net (zimbra.linuxsilo.net [92.48.122.79]) by mail.postgresql.org (Postfix) with ESMTP id 3873C6501D5 for ; Wed, 26 Nov 2008 04:39:08 -0400 (AST) Received: from localhost (localhost.localdomain [127.0.0.1]) by zimbra.linuxsilo.net (Postfix) with ESMTP id 30B352A695 for ; Wed, 26 Nov 2008 08:39:06 +0000 (GMT) X-Virus-Scanned: amavisd-new at Received: from zimbra.linuxsilo.net ([127.0.0.1]) by localhost (zimbra.linuxsilo.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gsto6Y91DkVw for ; Wed, 26 Nov 2008 08:39:05 +0000 (GMT) Received: from zimbra.linuxsilo.net (zimbra.linuxsilo.net [92.48.122.79]) by zimbra.linuxsilo.net (Postfix) with ESMTP id 4F68F28249 for ; Wed, 26 Nov 2008 08:39:05 +0000 (GMT) Date: Wed, 26 Nov 2008 08:39:05 +0000 (GMT) From: Jaume Sabater To: pgsql-admin@postgresql.org Message-ID: <29278214.7021227688745147.JavaMail.root@zimbra.linuxsilo.net> In-Reply-To: Subject: Re: Best option for expanding beyond 1 pg server in this situation MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Originating-IP: [212.170.239.110] X-Mailer: Zimbra 5.0.10_GA_2609.DEBIAN4.0 (ZimbraWebClient - FF3.0 (Win)/5.0.10_GA_2609.DEBIAN4.0) 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/147 X-Sequence-Number: 30801 ----- "Jamie Tufnell" escribi=C3=B3: =20 > 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? No, they are not. I have a PostgreSQL cluster at work with connection pooli= ng, replication and load balancing. It does failover and failback (online r= ecovery) via PCP commands of pgpool-II and it's working fine. Only real res= triction of pgpool-II is that you can't use CURRENT_TIMESTAMP, SERIALS and = such things that could produce different results on each node because the r= eplication happens by replicating SQL sentences. My next step is to try Master/Slave with pgpool-II and Slony-I. In this set= up, pgpool-II lets Slony-I do the replication and it does the rest of stuff= . As far as I know, Slony-I does not have the above mentioned restrictions = (not that we have them at work as we use an ORM, but I can understand that = for many people they are huge restrictions). > 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). As I said, I cannot talk about Slony-I yet, but your case is basically my c= ase, just that my database is 30 GB in size. pgpool-II is working fine by m= e. Given that inserts happen only because of nightly batch processes, I wou= ldn't really mind locking the tables if I had to use serials and such, alth= ough I would not like it. Hope this helps. If you have any more questions about pgpool-II, or if you = feel confused by the features in the README (I was, too, at the beginning),= please let me know. -- Jaume Sabater http://linuxsilo.net/ "Ubi sapientas ibi libertas"