linux-traipu team mailing list archive
-
linux-traipu team
-
Mailing list archive
-
Message #08019
[Bug 499596] Re: transaction_log plugin enable/disable sysvar does not work in call cases
Since we don't ship the basic transaction_log plugin, marking as Invalid
(even though in the past, this bug was valid)
** Changed in: drizzle
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Drizzle.
https://bugs.launchpad.net/bugs/499596
Title:
transaction_log plugin enable/disable sysvar does not work in call
cases
Status in A Lightweight SQL Database for Cloud Infrastructure and Web Applications:
Invalid
Status in Drizzle 7.0 series:
Fix Released
Status in Drizzle dexter series:
Won't Fix
Bug description:
The sysvar for enable/disabling the transaction_log plugin currently
is set to false by default when starting the server. If it is later
enabled in the terminal by doing "set global
transaction_log_enable=true;" This will result in the transaction_log
still not being initialized. The initialization code is in the init()
method and is blocked out by the sysvar to enable/disable the
transaction_log. A way to fix this is to attach a function call to
the sysvar variable so when its toggled the appropriate action is
taken. The tests dont see this because each test is run with
--transaction-log-enable on the command line for starting the server.
To manage notifications about this bug go to:
https://bugs.launchpad.net/drizzle/+bug/499596/+subscriptions