Re: Is ECC RAM necessary for MySQL server
Am 31.12.2011 14:03, schrieb Ryan Chan: Assume I am using InnoDB, which is ACID compliant. Do I still need to use ECC RAM, in order to make sure there is no chance of data corruption due data write? define necessary what has this to do with InnoDB / ACID if the underlying hardware makes a mistake there is no software which can make this unhappen because the software can not know that a ok written did never happen or did not write the expected data in my workstations i never used ECC-RAM, and hey i did not die on production servers i would always use server hardware where this normally is not a question signature.asc Description: OpenPGP digital signature
Re: Is ECC RAM necessary for MySQL server
Ryan, My opinion here. Any write to memory can go wrong, OS , MySQL , Storage engines, client library and so on. Innodb has some advanced mechanism for ACID compliance like the double write buffer but these are mostly to assure durability. Memory failure although not so frequent can still, in my opinion, corrupt anything included Innodb buffers. I would like the opinion of some other Innodb gurus. Happy new year. Claudio On Dec 31, 2011 2:04 PM, Ryan Chan ryanchan...@gmail.com wrote: Assume I am using InnoDB, which is ACID compliant. Do I still need to use ECC RAM, in order to make sure there is no chance of data corruption due data write? Thanks. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: Is ECC RAM necessary for MySQL server
On Sat, December 31, 2011 05:14, Claudio Nanni wrote: Ryan, My opinion here. Any write to memory can go wrong, OS , MySQL , Storage engines, client library and so on. Innodb has some advanced mechanism for ACID compliance like the double write buffer but these are mostly to assure durability. Memory failure although not so frequent can still, in my opinion, corrupt anything included Innodb buffers. I would like the opinion of some other Innodb gurus. Happy new year. Claudio On Dec 31, 2011 2:04 PM, Ryan Chan ryanchan...@gmail.com wrote: Assume I am using InnoDB, which is ACID compliant. Do I still need to use ECC RAM, in order to make sure there is no chance of data corruption due data write? Thanks. ECC memory helps ensure both the program and the data is correct. If you are running 24/7 operation rather than a test system which will be continually restarted, IMHO you need ECC memory. Otherwise you cannot guarantee that the instructions the program is executing is what the program writer intended. If the memory can have an error and your system cannot detect it ACID won't help, it will just ensure the error is reliably written to disk. -- William R. Mussatto Systems Engineer http://www.csz.com 909-920-9154 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: why does basic MySQLdump on db table fail with Permission denied, or else it creates a zero KB file
So then I try (in Mac OS X Terminal, while logged in as me (not root)): mysqldump -uroot -p myDBname myTableName ~/myTestDumpedTable.sql ...and again it produces: sh: mysqldump: command not found.. that is because Mac OSX is missing a package-managment and so you need a little knowledge about your OS to fix the PATH or you have to use full-qualified calls or configure/install your software to locations. How did you get your copy of MySQL? If you're using MacOS X Server, it should be in /usr/bin, which should be in your default $PATH, or else you couldn't do ANYTHING, including ls. And for the record, there are at least two excellent package managers available for Mac OS, and either MacPorts or Fink should append the proper path to their binaries to the $PATH variable so they can be found. (Although you need to log out and log back in to have your shell's .rc file executed.) Or else you built from source, in which case, you should know how to fix your $PATH. What does locate mysqldump tell you? How about echo $PATH? A gentleman of our days is one who has money enough to do what every fool would do if he could afford it: that is, consume without producing. -- George Bernard Shaw Jan Steinman, EcoReality Co-op -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: why does basic MySQLdump on db table fail with Permission denied, or else it creates a zero KB file
Am 31.12.2011 23:53, schrieb Jan Steinman: And for the record, there are at least two excellent package managers available for Mac OS, and either MacPorts or Fink if you call this package-managment from the view of a operating system you have never seen a real one - this are ADDITIONAL program/managers TRYING to do things OSX does not support signature.asc Description: OpenPGP digital signature
Re: why does basic MySQLdump on db table fail with Permission denied, or else it creates a zero KB file
So then I try (in Mac OS X Terminal, while logged in as me (not root)): mysqldump -uroot -p myDBname myTableName ~/myTestDumpedTable.sql ...and again it produces: sh: mysqldump: command not found.. that is because Mac OSX is missing a package-managment and so you need a little knowledge about your OS to fix the PATH or you have to use full-qualified calls or configure/install your software to locations. How did you get your copy of MySQL? I don't remember for sure.. but think I just went to the MySQL site and downloaded whatever looked like the right version for my environment. I used to use the one included with Mac OS 10.5, but when I upgraded to 10.6, then it no longer worked.. so I had to re-install MySQL. If you're using MacOS X Server, it should be in /usr/bin, which should be in your default $PATH, or else you couldn't do ANYTHING, including ls. And for the record, there are at least two excellent package managers available for Mac OS, and either MacPorts or Fink should append the proper path to their binaries to the $PATH variable so they can be found. (Although you need to log out and log back in to have your shell's .rc file executed.) Or else you built from source, in which case, you should know how to fix your $PATH. You may have guessed I am pretty much in over my head with running servers.. so I am just glad I have so far managed to do everything I need to develop, if not look smart on lists like this ;-) I have notes somewhere in my stuff about how to get $PATH to include where mysql actually lives, but once I realized what the issue was (in my OP this thread) then I was fine with just using a full path for now. The convenience of a 'fixed' $PATH will be nice, sooner or later (when I get to it), but for now it is just as well that I let it beat into my head how the CL is actually working (working out the full paths) What does locate mysqldump tell you? Govind% locate mysqldump WARNING: The locate database (/var/db/locate.database) does not exist. To create the database, run the following command: sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.locate.plist Please be aware that the database can take some time to generate; once the database has been created, this message will no longer appear. Govind% sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.locate.plist Password: Govind% locate mysqldump WARNING: The locate database (/var/db/locate.database) does not exist. To create the database, run the following command: sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.locate.plist Please be aware that the database can take some time to generate; once the database has been created, this message will no longer appear. Huh? Password was right.. but 'sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.locate.plist' seemed to have no effect. (Again, way over my head for now). How about echo $PATH? Govind% echo $PATH /usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/local/git/bin:/usr/X11/bin Thanks for poking :-) -Govinda -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
