In article <[EMAIL PROTECTED]>, Jeff Mathis <[EMAIL PROTECTED]> writes:
> my understanding is that the datafiles are created when the server > initializes, and this this is the designed and expected behavior. Most > other database products use a similar model. Your scenario cannot > happen. You specify how many innodb data files and how large in your > config file. when the server starts, it allocates all the space you > requested. if the server cannot find the space at startup, you get an > error. if during an import the file size is exceeded, you get an error > and the import stops. ... except if you use the "autoextend" clause on your innodb_data_file_path. In this case InnoDB files can grow automatically, but they can't shrink. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
