On Thu, 04 Nov 2010 17:10:54 -0000, David Shrewsbury <email address hidden> wrote:
> Pretty sure this is related to this newly merged branch:
>
> lp:~skinny.moey/drizzle/transaction_id_innodb
>
> Looks like an InnoDB trx id is allocated for the server STARTUP and
> SHUTDOWN events, but the transaction is never closed within InnoDB (via
> trx_free_for_mysql()).
This is quite likely.
Note that Innobase plugin will just start a transaction just about
anywhere if there hasn't been one... so calling things has to be pretty
careful.
we should add a test to storage_engine_api_tester for this call and what
sholud/shouldn't be aronud it.
On Thu, 04 Nov 2010 17:10:54 -0000, David Shrewsbury <email address hidden> wrote: for_mysql( )).
> Pretty sure this is related to this newly merged branch:
>
> lp:~skinny.moey/drizzle/transaction_id_innodb
>
> Looks like an InnoDB trx id is allocated for the server STARTUP and
> SHUTDOWN events, but the transaction is never closed within InnoDB (via
> trx_free_
This is quite likely.
Note that Innobase plugin will just start a transaction just about
anywhere if there hasn't been one... so calling things has to be pretty
careful.
we should add a test to storage_ engine_ api_tester for this call and what
sholud/shouldn't be aronud it.
--
Stewart Smith