My question is two-fold, first regarding error handing of table size limitations, and secondly performance and other implications of raid striping.
I'm building a system with an integrated MySQL database and there is a potential for filling up tables to the maximum file size for the OS I'm using (linux 2.2.x kernel, ext2 fs, 2gb max file size). I'd like to provide users with a graceful error-handling mechanism, essentially telling them: "The database is full. You must remove stuff before you can add more". Along with that, a % used number would be nice. Is there a method (through a mysql query) of determining how much space the database is taking up? It seems like the alternative is looking directly at the file system's record. Secondly, to get past the 2gb limit I'm considering using Raid Striping on a single partition. I'm curious if people have done this and what the performance implications are (how much worse is 2, 3, 10, 20 files than one file), and does doing this successfully avoid the 2gb limit (or is there some other limiting factor?) What is the next limiting factor beyond the file system's 2gb limit given unlimited storage? [that one is just curiosity] Thanks, Eric Mayers Software Engineer Captus Networks --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
