Sinisa Milivojevic <[EMAIL PROTECTED]> writes: > Steve Rapaport writes: > > Thanks to the guy who pointed this out. > > > > For the information of others, yes, it's quite possible > > to have a machine with mysql table files > 2GB lying about on the > > disk, that still doesn't properly support them. > > > > I had thought that if Mysql could create a 3GB file, > > it could use it. Bad assumption. > > > > This can get very confusing when Mysql uses these > > files then occasionally finds them corrupt for no > > apparent reason, then can't fix them. > > > > If your Index or database file approaches 2GB, and > > you are not CERTAIN that your file system and kernel > > both support LFS (Large File Support/Summit), you too may > > have inexplicable problems.... > > > > query, mysql, table > > -steve > > > > MySQL's limitation for file sizes on 32 bit systems is 1 Tb. > > All other limitations stem from filesystem limitations and MAX_ROWS > limitations.
Note that unrecommended usage of old compat compilers w/old compat glibc (egcs+glibc 2.1) may lead to this not working properly. MySQL needs to use current libraries with specified flags in order to use the *64 functions. -- Trond Eivind Glomsrød Red Hat, Inc. --------------------------------------------------------------------- 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
