Hi Heikki, I don't know if this has been requested, but what about a tool to 'pre-create' dataspace? This tool would allow someone to create a new dataspace, then a quick restart (After adding the name of the space to 'my.cnf') and the new dataspace is available! Maybe just extract the pieces from MySQL code and make it a separate tool?
I know I don't want to have a server shutdown while it creates 10GB of Dataspace! Of course autoextending is one answer. One could just create a small dataspace and let it autoextend. Thanks, Ken ----- Original Message ----- From: "Heikki Tuuri" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, March 03, 2002 6:46 AM Subject: Re: InnoDB frightens me... > Steve, > > I added an item to the TODO list at http://www.innodb.com/todo.html > > ...... > May, 2002: > Make a data file auto-extendible. You can specify the last data file in > innodb_data_file_path like this: > > ibdata1:50Mautoextend > > It will create a data file whose initial size is 50 MB, and InnoDB will > automatically extend it in units of 10 MB when the data file becomes full. > ...... > > Best regards, > > Heikki Tuuri > Innobase Oy > --- > Order technical MySQL/InnoDB support at https://order.mysql.com/ > Speed up adding of features to MySQL/InnoDB through support contracts > See http://www.innodb.com for the online manual and latest news on InnoDB > > > -----Original Message----- > From: Steve Rapaport <[EMAIL PROTECTED]> > Newsgroups: mailing.database.mysql > Date: Sunday, March 03, 2002 12:18 AM > Subject: InnoDB frightens me... > > > >I'm seriously considering switching to mysql-max so I can make my > >session handling table an Innodb type. Currently the mysql locking policy > >allows big traffic jams when several sessions are active simultaneously, > >and it's the only table that has frequent updates. I need row-locks! > > > >BUT, and it's a big but, > > > >I just read through the InnoDB manual pages in the mysql site, and > >it seems I can't have row-locking without a lot of programming > >and worse, admin overhead. And scary a-priori decisions. > > > >At first glance (correct me) I need to > >1. Check through all my programs handling this table to > >add AUTOCOMMIT or Commit/Rollback as appropriate. > > > >2. Decide with zero experience on a lot of maximum sizes which will not be > >adjustable in future, including dataspace. > > > >3. If I run up against one of those limits in future I am guaranteed > >a nightmare of table copying, deleting, restoring, and woe if I > >happen to get a "runaway rollback". I am also required to back > >up my database table and all its update logs in case of this situation, > >although my chances of restoring them successfully look dim. > > > >I am sufficiently frightened to just accept table-lock traffic jams > instead. > >Can anyone tell me how I can use row-locking without getting into > >this frightening world? > > > >Best, > >Steve > > > >--------------------------------------------------------------------- > >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 > > > > > > -------------------------------------------------------------------- - > 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 > > --------------------------------------------------------------------- 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
