MySQL to PostgreSQL Woes

I’ve had the last few days off, and my plan was to migrate BritBlog away from MySQL and on to PostgreSQL. The reason behind this awkward move is that our new and rather whizzy ping server/spider combination is sitting on top of PostgreSQL. Matt has done a great job with this (as you would expect if you knew him), so it’s just down to me now to fix up the BritBlog front end.

Anyway, I think I can say with complete confidence that I have wasted the entire three days:

• I’ve had problems converting a MySQL dump into something suitable for PostgreSQL to work with (I’m still getting import errors).
• I’ve forgotten what little I knew about PostgreSQL - need to wade through the documentation again.
• I’ve had problems getting Apache to run on my Windows laptop (I thought it would be more convenient to work on my laptop than at my desk).
• I’ve not even started updating the website code, nor have I gone anywhere near subversion yet.

I have, however, managed to get PuTTY working with public/private keys so I can access different servers more securely. Mind you that’s not really impressive when there are instructions as good as this to follow.

So all in all a total waste of time.

I think I’m going to start again, but will first nuke my laptop and put debian on it. Then I’ll have a perfectly working Linux, Apache, PHP, MySQL, PostgreSQL, Perl and Python setup - exactly what I need. Just wish I’d taken this course at the outset…

What a frustrating week! Sometimes I wish I could just lob my computer out of the window, unplug the web servers, and go live in a cave.

Tags: britblog, postgresql, mysql, aarrgghh