ARGH MySQL / PHP (again?)

I don't know if I've ranted on this last time, but it happened again with another site, so I shall rant again. For context, I'm the technical admin of a certain large site, which I won't even name due to NSFWness -- I'm just mentioning it here so that visitors from that site know who I am :) A brief timeline of events:

In contrast, my preferred database server, Postgres, ran fine throughout the incident -- read-only requests were served as normal, and if anything tried to add data it would be told "the disk is full"; no crashing, no corrupt data, no problem. Also, it seems to scale better, currently dealing with a database of 8 * the size of RAM quite happily.

It's 7am, so I'm going to bed now; first thing I do when I wake up will be start work on giving this app Postgres support; then I can uninstall mysql since nothing else needs it \o/

2008-01-06 18:17:40 -0600
Previous Index Next