Re: [PERFORM] Database conversion woes...

2004-02-06 Thread Kevin Carpenter
First just wanted to say thank you all for the quick and helpful answers. With all the input I know I am on the right track. With that in mind I created a perl script to do my migrations and to do it based on moving from a db name to a schema name. I had done alot of the reading on convertin

Re: [PERFORM] Database conversion woes...

2004-02-03 Thread Richard Huxton
On Tuesday 03 February 2004 22:29, Kevin wrote: > The mammoth replicator has been working well. I had tried > the pgsql-r and had limited success with it, and dbmirror was just > taking to long having to do 4 db transactions just to mirror one > command. I have eserv but was never really a java k

Re: [PERFORM] Database conversion woes...

2004-02-03 Thread Christopher Browne
[EMAIL PROTECTED] ("Kevin Carpenter") writes: > I am doing a massive database conversion from MySQL to Postgresql for a > company I am working for. This has a few quirks to it that I haven't > been able to nail down the answers I need from reading and searching > through previous list info. > > Fo

Re: [PERFORM] Database conversion woes...

2004-02-03 Thread Richard Huxton
On Tuesday 03 February 2004 16:42, Kevin Carpenter wrote: > > Thanks in advance, will give more detail - just looking for some open > directions and maybe some kicks to fuel my thought in other areas. I've taken to doing a lot of my data manipulation (version conversions etc) in PG even if the fi

Re: [PERFORM] Database conversion woes...

2004-02-03 Thread Josh Berkus
Kevin, > With the size of each single db, I 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

Re: [PERFORM] Database conversion woes...

2004-02-03 Thread scott.marlowe
On Tue, 3 Feb 2004, Kevin Carpenter wrote: > Hello everyone, > > I am doing a massive database conversion from MySQL to Postgresql for a > company I am working for. This has a few quirks to it that I haven't > been able to nail down the answers I need from reading and searching > through previou

Re: [PERFORM] Database conversion woes...

2004-02-03 Thread Jeff
On Tue, 03 Feb 2004 11:42:59 -0500 "Kevin Carpenter" <[EMAIL PROTECTED]> 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