X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id C2CB1D1D2DB for ; Tue, 3 Feb 2004 16:57:52 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 17839-03 for ; Tue, 3 Feb 2004 12:57:50 -0400 (AST) Received: from jefftrout.com (h00a0cc4084e5.ne.client2.attbi.com [24.128.241.68]) by svr1.postgresql.org (Postfix) with SMTP id 9BD13D1C9FB for ; Tue, 3 Feb 2004 12:57:47 -0400 (AST) Received: (qmail 34973 invoked from network); 3 Feb 2004 16:57:51 -0000 Received: from localhost (HELO squeegit) (threshar@127.0.0.1) by localhost with SMTP; 3 Feb 2004 16:57:51 -0000 Date: Tue, 3 Feb 2004 12:00:34 -0500 From: Jeff To: kevin@valenfor.com Cc: pgsql-performance@postgresql.org Subject: Re: Database conversion woes... Message-Id: <20040203120034.78adcc5c.threshar@torgo.978.org> In-Reply-To: References: X-Mailer: Sylpheed version 0.9.9 (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/47 X-Sequence-Number: 5571 On Tue, 03 Feb 2004 11:42:59 -0500 "Kevin Carpenter" wrote: > For starters, I am moving roughly 50 seperate databases which each one > represents one of our clients and is roughly 500 megs to 3 gigs in > size. > Currently we are using the MySQL replication, and so I am looking at > Mammoths replicator for this one. However I have seen it only allows > on DB to be replicated at a time. With the size of each single db, I Not knowing too much about mammoths, but how the others work, you should be able to run a replicator for each db. (Or hack a shell script up to make it run the replicator for each db.. either way each db will be replicated independant of the others) > don't know how I could put them all together under one roof, and if I > was going to, what are the maximums that Postgres can handle for > tables in one db? We track over 2 million new points of data > (records) a day, and are moving to 5 million in the next year. >