X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 57F5052957 for ; Wed, 30 Mar 2005 00:34:26 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 27659-08 for ; Tue, 29 Mar 2005 23:34:17 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.204]) by svr1.postgresql.org (Postfix) with ESMTP id 9847D5294E for ; Wed, 30 Mar 2005 00:34:16 +0100 (BST) Received: by wproxy.gmail.com with SMTP id 68so794228wri for ; Tue, 29 Mar 2005 15:34:19 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=Sf2xOEEQAIZIPPWGzzKDbohH1GFAnehgaRITlKByNuy7ze45HKZESUffcROkkoTxHmM1H/qXkriCS4xnpJvOWD4l54ywybxoNruMWAlR/FbM2iApZ7Gk38WuUnIypyseSnl2oUc3Tb48XD5xVU+ah0rBhlgoyGKhbjGCPoNB8do= Received: by 10.54.51.9 with SMTP id y9mr64387wry; Tue, 29 Mar 2005 15:34:19 -0800 (PST) Received: by 10.54.40.23 with HTTP; Tue, 29 Mar 2005 15:34:19 -0800 (PST) Message-ID: Date: Tue, 29 Mar 2005 15:34:19 -0800 From: David B Reply-To: David B To: pgsql-admin@postgresql.org Subject: Replication solutions high volume db Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.821 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE, FROM_ENDS_IN_NUMS, RCVD_BY_IP X-Spam-Level: X-Archive-Number: 200503/467 X-Sequence-Number: 16965 Folks, I'm thinking of replication tools for high volume site. Postgres on dual Opteron box. 1/2 GB of data. Big overnight load of data. Some inserts during the data but mostly selects. I think I've narrowed it down to Slony and Mammoth. Any pro's or con's on one vs the other? There is the obvious price difference but thats managable if Mammoth substancially better. Some area where our environement might stretch a solution. Some records can be large. Limitied to one table but they can be 40K+ of chraracters in a column. High volume of inserts coming during nightly load (millions of rows). These loads are coming in commited blocks of 100. That cannot slow down the replication. Our call center agents needs access to them asap. Any locking issues on the master during the replication process? Anything else I should be concerned about or things I need to consider? Personal experiences you have had running either. tia David