From: Jeff <threshar@torgo.978.org>
To: kevin@valenfor.com
Cc: pgsql-performance@postgresql.org
Subject: Re: Database conversion woes...
Date: Tue, 3 Feb 2004 12:00:34 -0500
Message-ID: <20040203120034.78adcc5c.threshar@torgo.978.org> (raw)
In-Reply-To: <E1Ao3db-0002sp-EL@alexandria15.alexsrv15.com>
References: <E1Ao3db-0002sp-EL@alexandria15.alexsrv15.com>
On Tue, 03 Feb 2004 11:42:59 -0500
"Kevin Carpenter" <kevin@valenfor.com> 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.
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: threshar@torgo.978.org, kevin@valenfor.com
Subject: Re: Database conversion woes...
In-Reply-To: <20040203120034.78adcc5c.threshar@torgo.978.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox