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 B920AD1CACB for ; Tue, 3 Feb 2004 19:30:12 +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 90336-07 for ; Tue, 3 Feb 2004 15:30:02 -0400 (AST) Received: from anchor-post-37.mail.demon.net (anchor-post-36.mail.demon.net [194.217.242.86]) by svr1.postgresql.org (Postfix) with ESMTP id 2AD20D1D2DB for ; Tue, 3 Feb 2004 15:29:56 -0400 (AST) Received: from mwynhau.demon.co.uk ([193.237.186.96] helo=mainbox.archonet.com) by anchor-post-37.mail.demon.net with esmtp (Exim 3.35 #1) id 1Ao6FA-0002C9-0b; Tue, 03 Feb 2004 19:29:56 +0000 Received: by mainbox.archonet.com (Postfix, from userid 529) id 1481A166A1; Tue, 3 Feb 2004 19:29:55 +0000 (GMT) Received: from client17.archonet.com (client17.archonet.com [192.168.1.17]) by mainbox.archonet.com (Postfix) with ESMTP id CFB6C16587; Tue, 3 Feb 2004 19:29:52 +0000 (GMT) From: Richard Huxton To: kevin@valenfor.com, pgsql-performance@postgresql.org Subject: Re: Database conversion woes... Date: Tue, 3 Feb 2004 19:29:52 +0000 User-Agent: KMail/1.5 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200402031929.52383.dev@archonet.com> X-Bogosity: No, tests=bogofilter, spamicity=0.000000, version=0.15.3 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/54 X-Sequence-Number: 5578 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 final resting place is MySQL. It's generally not too difficult to transfer data but you will have problems with MySQL's more "relaxed attitude" to data types (things like all-zero timestamps). I tend to write a script to tidy the data before export, and repeatedly restore from backup until the script corrects all problems.Not sure how convenient that'll be with dozens of gigs of data. Might be practical to start with the smaller databases, let your script grow in capabilities before importing the larger ones. -- Richard Huxton Archonet Ltd