Circling back:
upsteam bug #67433 has been closed. The unsafe syntax will be removed
in 5.5.41/5.6.22 (not yet released).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1357003
** Bug watch added: MySQL Bug System #67433
http://bugs.mysql.com/bug.php?id=67433
** Also affects: mysql-server via
http://bugs.mysql.com/bug.php?id=67433
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Public bug reported:
Per:
http://www.tocker.ca/2014/08/14/set-global-sql_log_bin-we-need-your-feedback.html
Upstream MySQL is proposing to change the following syntax to produce an
error in current GA releases (5.5 and 5.6):
mysql SET GLOBAL sql_log_bin = x;
The rationale for this is:
- The
I can confirm that this bug is fixed by upstream in 5.5.36 (latest). I
believe it might be http://bugs.mysql.com/bug.php?id=68749
Here's the results of the testcase showing expected output:
morgo@Rbook:~/sandboxes/msb_5_5_36$ ./use ~/Desktop/testdump6.sql.txt
count(distinct(testtab.foo))
111
I've filed a feature request with upstream. In 5.1/5.5 the InnoDB
storage engine will have a background thread that wakes up every one
second.
In future versions there will be more threads for background work (as
this is required for multi-core scalability), so it is an interesting
question how
Just noting upstream's policy (commented on MySQL bug as well) -
5.1 has entered 'sustaining support', and won't be eligible for a
backported patch. Decision to carry the patch would have to lie with
Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Server Team,
