Path: csiph.com!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: Dimitri Fontaine Newsgroups: comp.databases.postgresql Subject: Re: migrate from mysql to pgsql Date: Sun, 31 Jan 2016 22:19:29 +0100 Organization: A noiseless patient Spider Lines: 21 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain Injection-Info: mx02.eternal-september.org; posting-host="d82aa4f1883ab7155c995516303c9b46"; logging-data="15651"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/JuUGey76o3ZnuuYHPyS6M" User-Agent: Gnus/5.13001 (Ma Gnus v0.10) Emacs/24.5 (darwin) Cancel-Lock: sha1:hFZ7fIJKezVYORTEbb3LxbXnJaw= sha1:x/2GUwntsSbDJq7uIc7t/8MNC90= Xref: csiph.com comp.databases.postgresql:704 Magnus Warker writes: > There are situations where I want to decide for myself what to do, e. g. if > there is a datatype in MySQL that's not present in PgSql. That's covered in the load command, and in the --cast command line switch. > I see your point, but I think it also depends on the migration strategy. I > had to do a lot of manual work, but I prefer to do it carefully step by step > to having things automated too much. In my opinion, the more complex the migration is, the more you want to automate it completely, with test cases that you can run nigthly and from which you can analyze problems the next day. Do the full migration once a day for a couple months while you fix the application so that you're confident no surprise will jump at you on D-day: you've been doing that before. -- Dimitri Fontaine PostgreSQL DBA, Architecte