On Mon, 20 Jun 2011 02:39:49 -0000, Laurynas Biveinis <email address hidden> wrote:
> Stewart, I don't have a strong opinion about the best action for 5.5 and
> welcome any input from others.
>
> We want to avoid any nasty surprises for the user during the 5.1 -> 5.5
> upgrade, and for upstream -> PS upgrade too. For the context, in 5.5
> upstream the server with ignore-builtin-innodb will fail to start unless
> default-storage-engine=MyISAM is given too. Now having these two options
> already, the only way still to have InnoDB is to have it compiled as
> plugin and do plugin-load=innodb=ha_innodb.so. (I am not sure if
> default-storage-engine=MyISAM is still required then for the server to
> start).
Keeping upstream behaviour is okay. We should probably warn in docs however.
On Mon, 20 Jun 2011 02:39:49 -0000, Laurynas Biveinis <email address hidden> wrote: builtin- innodb will fail to start unless storage- engine= MyISAM is given too. Now having these two options load=innodb= ha_innodb. so. (I am not sure if storage- engine= MyISAM is still required then for the server to
> Stewart, I don't have a strong opinion about the best action for 5.5 and
> welcome any input from others.
>
> We want to avoid any nasty surprises for the user during the 5.1 -> 5.5
> upgrade, and for upstream -> PS upgrade too. For the context, in 5.5
> upstream the server with ignore-
> default-
> already, the only way still to have InnoDB is to have it compiled as
> plugin and do plugin-
> default-
> start).
Keeping upstream behaviour is okay. We should probably warn in docs however.
--
Stewart Smith