How to convert an existing RT from Postgres to MySQL?

Someone wants me to convert their Postgres backed RT to MySQL. Doesn’t
matter why, they want it. :slight_smile:

Here’s what I am thinking.

  1. Shut down the web server.
  2. Dump the DB data.
  3. Reconfigure RT for MySQL.
  4. Run initdb
  5. Load the data.
  6. Restart the RT/web server.

Have I covered all my bases? Are there any wrinkles to this Postgres ->
MySQL move that I need to be aware of?

Thanks!

Todd Chapman wrote:

Someone wants me to convert their Postgres backed RT to MySQL. Doesn’t
matter why, they want it. :slight_smile:

Here’s what I am thinking.

  1. Shut down the web server.
  2. Dump the DB data.
  3. Reconfigure RT for MySQL.
  4. Run initdb
  5. Load the data.
  6. Restart the RT/web server.

You’re probably in trouble between points 4 and 5 since initdb does
create not only the db objects but also loads data which will be in the
dataset that comes from postgres, if you’re lucky the inital data will
be the same but I wouldn’t bet on it. You could truncate the tables and
reset the sequences but it might be easier to modify initdb to only
create but not load the data.

Joop

Good point Joop! I’ll make sure the initial data doesn’t get inserted.
Thanks!

-ToddOn Tue, Jun 17, 2008 at 2:21 AM, Joop JoopvandeWege@mococo.nl wrote:

Todd Chapman wrote:

Someone wants me to convert their Postgres backed RT to MySQL. Doesn’t
matter why, they want it. :slight_smile:

Here’s what I am thinking.

  1. Shut down the web server.
  2. Dump the DB data.
  3. Reconfigure RT for MySQL.
  4. Run initdb
  5. Load the data.
  6. Restart the RT/web server.

You’re probably in trouble between points 4 and 5 since initdb does create
not only the db objects but also loads data which will be in the dataset
that comes from postgres, if you’re lucky the inital data will be the same
but I wouldn’t bet on it. You could truncate the tables and reset the
sequences but it might be easier to modify initdb to only create but not
load the data.

Joop