Hot answers tagged crash
TL;DR: Except for a specific bug in PostgreSQL 9.3 prior to 9.3.4 which it's vital that you patch, index corruption after crash is never expected and hasn't been since PostgreSQL 7.1 was released in 2001. The advice/folklore you got was wrong. I am told that a long time ago in a galaxy far, far away (PostgreSQL 8.4 under Ubuntu 12.04), PostgreSQL ...
You can do many things to prevent this. Move DB server to somewhere else (hosting) Buy an UPS Change to a simpler DB software (SQLite, Files) Make your code to always save the latest changes, so when power up, programs keep running from last saved point.
I'm sorry, I don't have a corrupt pg_conversion table to help perform any verifications. My answers here must, by necessity, be heavily based on speculation. With the limited information we have, I am guessing that you are attempting to do a full database pg_dump, along the lines of pg_dump --host 127.0.0.1 --port 5432 --username "postgres" ... ...
You will have to mysqldump around moments_production_wp I have old posts to bypass databases and tables Dec 16, 2011 : How do you mysqldump specific table(s)? Feb 20, 2013 : There is any option for mysqldump to ignore databases for backup in mysql Using the same concepts, here is how to mysqldump all except moments_production_wp MYSQL_USER=root ...
I am not totally convinced MySQL is running out of memory. Here is why: ASPECT #1 When you use mysqltuner.pl, it calculates the total usage in the worst case scenario. It does it by adding 3 figures together key_buffer_size innodb_buffer_pool_size thread_memory : max_connections * the sum of sort_buffer_size join_buffer_size read_buffer_size ...
After a bunch more googling, etc., I finally came upon the solution: http://notesonit.blogspot.hk/2013/05/innodb-unable-to-lock-ibdata1-error-11.html
Only top voted, non community-wiki answers of a minimum length are eligible