From: Vladislav Vaintroub
Date: June 15 2011 8:03pm
Subject: RE: bzr commit into mysql-trunk branch (vasil.dimov:3194)
List-Archive: http://lists.mysql.com/commits/139268
Message-Id: <001801cc2b97$5be9b240$13bd16c0$@montyprogram.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

> -----Original Message-----
> From: vasil.dimov@stripped [mailto:vasil.dimov@stripped]
> Sent: Mittwoch, 15. Juni 2011 10:03
> To: commits@stripped
> Subject: bzr commit into mysql-trunk branch (vasil.dimov:3194)
> 
> #At file:///usr/local/devel/bzrroot/server/mysql-trunk/ based on
> revid:anitha.gopi@stripped
> 
>  3194 Vasil Dimov	2011-06-15
>       Install InnoDB persistent stats tables during db install time
>       (from the script mysql_install_db).
> 

Hi Vasil,
I think this is problematic. mysql_install_db never installed innodb
anything, so user had a possibility to correctly size innodb in
my.cnf/my.ini  before the first start. Now, bootstrap won't be reading any
my.cnf and creates spaces in their default size. Not everyone would like it
this way and not everyone is prepared for it  - I'm quite sure your new
Windows  installer and old Configwizard will both fail because of incorrect
log file size.  One could eliminate some hassle , if Innodb team fixes
complexity around changing innodb_log_file_size, so database starts even if
the value is just changed in my.cnf or in startup parameters..

Wlad