Anyone familiar with how to deal with innodb corruption in regards to mysql tables and databases?
what kind of corruption?  ran out of disk space?
http://www.mysqlperformanceblog.com/2008/07/04/recovering-innodb-table-corruption/  <-- this helped me the last time I dealt with innodb corruption.
mnathani: upgrade to postgres before its too late?? ;-)
jpalmer: thanks, crappy non-ARP VPS host kills all processes when memory consumption reaches a certain threshold. No SWAP allowance either. Just a hard limit on memory usage
toddf: do wordpress and drupal even run on postgres?
oh and the VPS host, rather than investigate what is using up so much memory, suggested multiple times to simply upgrade my plan to fix the problem.
mnathani: is it openvz?
mnathani: drupal I can vouch for works with postgres at its core, some modules need a regex lesson in schema templates for postgres, and a few other easily fixed tweaks here and there last I tried it. wordpress? can't say I've tried it, but its just sql storage, how hard can it be?
hazardous: Virtuozzo I believe
so basically openvz
your beancounters are probably screwed beyond wonder
hazardous: cat /proc/user_beancounters >> http://pastebin.com/AvULcPyW  Not sure how to interpret the results though