Two cents from me:
This looks like an InnoDB assertion (a deliberate crash because the data file
is in an inconsistent state, and proceeding is considered unsafe). Assertions
can either be the result of an unsafe shutdown with non-durable settings (or
hardware) or bugs in MySQL code.
--
You
Hi!
mysqlhotcopy has been deprecated by upstream (and removed in 5.7). I have a
blog post on it here:
http://www.tocker.ca/2014/04/17/proposal-to-deprecate-mysqlhotcopy.html
Most importantly, it will not safely back up InnoDB tables (which is the
default storage engine from 5.5+).
--
You
@druss: Log-slow-verbosity is a Percona Server feature. The behavior of
mysql config options is that if they are unknown the server refuses to
start. This is useful, since if the server were to start based on a
typo in config, it could behave drastically different.
--
You received this bug
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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1357003
Title:
SET GLOBAL
To add context, the future version this will be deprecated in is MySQL
5.7. From http://dev.mysql.com/doc/refman/5.7/en/mysql-nutshell.html :
The --key-buffer option must now be specified as --key-buffer-size.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** 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,
** 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
Bugs, which is
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
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
It is worth mentioning that in MySQL 5.7, the test database is removed
by default. A root password is also randomly generated, and on first
login the root user will be required to change it.
A password policy will also apply, by default: 8 characters in length.
--
You received this bug
*** This bug is a duplicate of bug 1256931 ***
https://bugs.launchpad.net/bugs/1256931
Duplicates https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1256931
5.6 is available in universe in Trusty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Just a brief comment from upstream:
Turning off query cache is an acceptable resolution. It is off by default from
MySQL 5.6+
http://www.tocker.ca/2013/09/10/improving-mysqls-default-configuration.html
(The query cache mutex is hot on multi-core systems.)
--
You received this bug
The references on the mysqlperformanceblog.com post link to two upstream bugs:
MySQL Bug #68045
MySQL Bug #68045
Both have since been fixed, and with Ubuntu now at 5.5.35 should this
bug be closed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
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
I think this sounds like a reasonable feature request to track with
upstream. I've filed: http://bugs.mysql.com/bug.php?id=71659
** Bug watch added: MySQL Bug System #71659
http://bugs.mysql.com/bug.php?id=71659
--
You received this bug notification because you are a member of Ubuntu
Bugs,
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,
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
Bugs, which
21 matches
Mail list logo
