From: Richard Huxton <dev@archonet.com>
To: kevin@valenfor.com
To: pgsql-performance@postgresql.org
Subject: Re: Database conversion woes...
Date: Tue, 3 Feb 2004 19:29:52 +0000
Message-ID: <200402031929.52383.dev@archonet.com> (raw)
In-Reply-To: <E1Ao3db-0002sp-EL@alexandria15.alexsrv15.com>
References: <E1Ao3db-0002sp-EL@alexandria15.alexsrv15.com>
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
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: dev@archonet.com, kevin@valenfor.com
Subject: Re: Database conversion woes...
In-Reply-To: <200402031929.52383.dev@archonet.com>
* 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