Percona Server moved to https://jira.percona.com/projects/PS

Merge lp:~hrvojem/percona-server/rn-5.5.30-30.2 into lp:percona-server/5.5

  1. rn-5.5.30-30.2
  2. Merge into 5.5
Proposed by Hrvoje Matijakovic
Status: Merged
Approved by: Alexey Kopytov
Approved revision: no longer in the source branch.
Merged at revision: 500
Proposed branch: lp:~hrvojem/percona-server/rn-5.5.30-30.2
Merge into: lp:percona-server/5.5
Diff against target: 404 lines (+160/-64)
6 files modified
doc/source/conf.py (+1/-1)
doc/source/performance/innodb_lazy_drop_table.rst (+5/-0)
doc/source/performance/threadpool.rst (+32/-45)
doc/source/release-notes/Percona-Server-5.5.30-30.2.rst (+73/-0)
doc/source/release-notes/release-notes_index.rst (+1/-0)
doc/source/upstream-bug-fixes.rst (+48/-18)
To merge this branch: bzr merge lp:~hrvojem/percona-server/rn-5.5.30-30.2
Reviewer Review Type Date Requested Status
Alexey Kopytov (community) Approve
Laurynas Biveinis (community) Approve
Review via email: mp+157869@code.launchpad.net

Description of the change

NOTE: This is not a GCA branch but lp:percona-server/5.5 as the GCA would introduce the conflicts

To post a comment you must log in.
Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote :

    - Mentioning only that innodb_lazy_drop_table has been deprecated
      is not enough when in fact the feature has been removed and its
      controlling variable has been made a deprecated no-op. These
      points should be mentioned and also rationale for removing the
      feature in the first place should be provided, both in release
      notes and in in the feature doc.
    - I'd add to the RN introduction, next to the features, that a
      number of performance bugs have been fixed in this release
    - Diff line 52: s/remains/may remain.
    - Diff line 61; s/it first checks/first it checks or it checks
      ... first.
    - Bug 1086227 and 1128848 need description.
    - Bug 1108613, I'd add that this is a corner case.
    - Bug 1162085: need to be more specific re. failure circumstances
      (binlogging with very large log events).
    - Bug 1125248: "potentially improve XtraDB performance by
      optimizing innodb_pass_corrupt_table value checks for the
      common case of innodb_pass_corrupt_table equal to 0."
    - Diff line 206: s/upsream/upstream
    - Bug 1107539: is relevant for operation under threadpool only.

review: Needs Fixing
Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote :

Heads-up re. bug 1146621 being added to the milestone, to be listed under "other bugs fixed"

review: Needs Fixing
Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote :

    - I wonder why the bugfixes get credits and features do not. In
      the old RNs I see the features used to get credits too. So
      let's assign credit for the features as well. High prio queues
      and performance fixes Alexey Kopytov, jemalloc Alexey Stroganov
      and Ignacio Nin, perf bugs Alexey Kopytov, drop table me.

    - Bug 1086227 and 1128848 missing variable reference, s/the DDL
      statement/a DDL statement.

    - Bug 1162085 s/very large/large, they are only in tens of KBs.

review: Needs Fixing
Revision history for this message
Laurynas Biveinis (laurynas-biveinis) :
review: Approve
Revision history for this message
Alexey Kopytov (akopytov) wrote :

- The only thing for this release we did wrt jemalloc is just packaged
  it into our repositories. The jemalloc server plugin implemented by
  Alexey Stroganov has not been merged (and thus, the credits are wrong)

- I don't see the point in mentioning "numerous performance fixes". We
  already list all bugs fixed below, why mention it twice?

- s/restoring the secondary key to the table schema/omitting the
  corresponding secondary keys from deferred key creation optimization/

- s/from the *MariaDB*/from |MariaDB|/

- the fix for bug #1127008 also applies to CREATE TABLE ... IF NOT
  EXITS. I suggest the following wording:

  "
  ``CREATE TABLE`` or ``CREATE TABLE IF NOT EXISTS`` statements
  on an existing table could wait on a metadata lock instead of failing
  or returning immediately.
  "

- s/introduced the regression/introduced a regression/

- the events for bug #1162085 did not have to be large. I suggest the
  following wording:

  "
  Fix for bug :bug:`1070856` introduced a regression in |Percona Server|
  :rn:`5.5.28-29.3` which could cause a server to hang when binary log
  is enabled. Bug fixed :bug:`1162085`.
  "

- suggested entry for #1131187:

  "
  Fixed upstream bug :mysqlbug:`49169` by avoiding the ``malloc`` call
  in the ``read_view_create_low()`` in most cases. This significantly
  improves InnoDB scalability on read-only workloads, especially when
  the default glibc memory allocator is used.
  "

- suggested entry for #1131189:

  "
  Removed ``trx_list`` scan in ``read_view_open_now()`` which is another
  problem originally reported as upstream bug :mysqlbug:`49169`. This
  also provides much better scalability in InnoDB high-concurrent workloads.
  "

- suggested entry for #1125248:

  "
  Reduced the overhead from `innodb_pass_corrupt_table`` value checks by
  optimizing them for better CPU branch prediction.
  "

- suggested entry for #1163439:

  " Fixed the upstream bug :mysqlbug:`68845` which could unnecessarily
  increase contention on ``log_sys->mutex`` in write-intensive
  workloads. Bug fixed :bug:`1163439`
  "

- should this MP also document all upstream bug fixes in
  upstream-bug-fixes.rst?

review: Needs Fixing
Revision history for this message
Alexey Kopytov (akopytov) wrote :

Sorry, s/binary log is enabled/the binary log was enabled/

Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote :

> - I don't see the point in mentioning "numerous performance fixes". We
> already list all bugs fixed below, why mention it twice?

The list of the bugs provides all the information, but it's also quite long. IMHO there is value in stating the focus areas in bugfixing for a release, when there are any, and the number of fixed bugs warrants it, and for this release it was the performance fixes.

Revision history for this message
Alexey Kopytov (akopytov) wrote :

Hi Laurynas,

On Wed, 10 Apr 2013 12:26:23 -0000, Laurynas Biveinis wrote:
>> - I don't see the point in mentioning "numerous performance fixes". We
>> already list all bugs fixed below, why mention it twice?
>
> The list of the bugs provides all the information, but it's also quite long. IMHO there is value in stating the focus areas in bugfixing for a release, when there are any, and the number of fixed bugs warrants it, and for this release it was the performance fixes.
>
>

Then let's do "s/numerous/a number of/" at least.

Revision history for this message
Alexey Kopytov (akopytov) :
review: Approve

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'doc/source/conf.py'
2--- doc/source/conf.py 2013-03-06 06:41:38 +0000
3+++ doc/source/conf.py 2013-04-10 13:09:24 +0000
4@@ -54,7 +54,7 @@
5 # The short X.Y version.
6 version = '5.5'
7 # The full version, including alpha/beta/rc tags.
8-release = '5.5.30-30.1'
9+release = '5.5.30-30.2'
10
11 # The language for content autogenerated by Sphinx. Refer to documentation
12 # for a list of supported languages.
13
14=== modified file 'doc/source/performance/innodb_lazy_drop_table.rst'
15--- doc/source/performance/innodb_lazy_drop_table.rst 2012-12-14 09:58:23 +0000
16+++ doc/source/performance/innodb_lazy_drop_table.rst 2013-04-10 13:09:24 +0000
17@@ -4,6 +4,10 @@
18 Drop table performance
19 ======================
20
21+.. warning::
22+
23+ This feature has been removed and its controlling variable :variable:`innodb_lazy_drop_table` has been deprecated from |Percona Server| :rn:`5.5.30-30.2`. Feature has been removed because the upstream ``DROP TABLE`` implementation has been improved.
24+
25 When *innodb_file_per_table* is set to 1, doing a DROP TABLE can take a long time on servers with a large buffer pool, even on an empty |InnoDB| table. This is because InnoDB has to scan through the buffer pool to purge pages that belong to the corresponding tablespace. Furthermore, no other queries can start while that scan is in progress.
26
27 This feature allows you to do "background table drop".
28@@ -12,6 +16,7 @@
29 ============================
30
31 * :rn:`5.5.10-20.1` Feature added.
32+ * :rn:`5.5.30-30.2` Feature deprecated.
33
34 System Variables
35 ================
36
37=== modified file 'doc/source/performance/threadpool.rst'
38--- doc/source/performance/threadpool.rst 2013-04-04 10:52:07 +0000
39+++ doc/source/performance/threadpool.rst 2013-04-10 13:09:24 +0000
40@@ -24,11 +24,24 @@
41
42 Current implementation of the thread pool is built in the server, unlike the upstream version which is implemented as a plugin. Another significant implementation difference is that this implementation doesn't try to minimize the number of concurrent transactions like the ``MySQL Enterprise Threadpool``. Because of these things this implementation isn't compatible with the upstream one.
43
44-.. note::
45-
46- Percona Server adds priority scheduling to the original
47-implementation introduced in |MariaDB|. See description of the
48-:variable:`thread_pool_high_prio_tickets` below.
49+Priority connection scheduling
50+==============================
51+
52+In |Percona Server| :rn:`5.5.30-30.2` priority connection scheduling for thread pool has been implemented. Even though thread pool puts a limit on the number of concurrently running queries, the number of open transactions may remain high, because connections with already started transactions are put to the end of the queue. Higher number of open transactions has a number of implications on the currently running queries. To improve the performance new :variable:`thread_pool_high_prio_tickets` variable has been introduced.
53+
54+This variable controls the high priority queue policy. Each new connection is assigned this many tickets to enter the high priority queue. Whenever a query has to be queued to be executed later because no threads are available, the thread pool puts the connection into the high priority queue if the following conditions apply:
55+
56+ 1. The connection has an open transaction in the server.
57+ 2. The number of high priority tickets of this connection is non-zero.
58+
59+If both the above conditions hold, the connection is put into the high priority queue and its tickets value is decremented. Otherwise the connection is put into the common queue with the initial tickets value specified with this option.
60+
61+Each time the thread pool looks for a new connection to process, first it checks the high priority queue, and picks connections from the common queue only when the high priority one is empty.
62+
63+The goal is to minimize the number of open transactions in the server. In many cases it is beneficial to give short-running transactions a chance to commit faster and thus deallocate server resources and locks without waiting in the same queue with other connections that are about to start a new transaction, or those that have run out of their high priority tickets.
64+
65+With the default value of 0, all connections are always put into the common queue, i.e. no priority scheduling is used as in the original implementation in |MariaDB|. The higher is the value, the more chances each transaction gets to enter the high priority queue and commit before it is put in the common queue.
66+
67
68 Version Specific Information
69 ============================
70@@ -36,6 +49,9 @@
71 * :rn:`5.5.29-30.0`
72 ``Thread Pool`` feature implemented. This feature was ported from |MariaDB|.
73
74+ * :rn:`5.5.30-30.2`
75+ Implemented priority connection scheduling and introduced new variable :variable:`thread_pool_high_prio_tickets` to the original implementation introduced in |MariaDB|.
76+
77 System Variables
78 ================
79
80@@ -50,6 +66,17 @@
81
82 This variable can be used to limit the time an idle thread should wait before exiting.
83
84+.. variable:: thread_pool_high_prio_tickets
85+
86+ :cli: Yes
87+ :conf: Yes
88+ :scope: Global
89+ :dyn: Yes
90+ :vartype: Numeric
91+ :default: 0
92+
93+This variable controls the high priority queue policy. Each new connection is assigned this many tickets to enter the high priority queue.
94+
95 .. variable:: thread_pool_max_threads
96
97 :cli: Yes
98@@ -94,46 +121,6 @@
99
100 The number of milliseconds before a running thread is considered stalled. When this limit is reached thread pool will wake up or create another thread. This is being used to prevent a long-running query from monopolizing the pool.
101
102-.. variable:: thread_pool_high_prio_tickets
103-
104- :cli: Yes
105- :conf: Yes
106- :scope: Global
107- :dyn: Yes
108- :vartype: Numeric
109- :default: 0
110-
111-This variable controls the high priority queue policy. Each new
112-connection is assigned this many tickets to enter the high priority
113-queue. Whenever a query has to be queued to be executed later because no
114-threads are available, the thread pool puts the connection into the high
115-priority queue if the following conditions apply:
116-
117-1. The connection has an open transaction in the server.
118-2. The number of high priority tickets of this connection is non-zero.
119-
120-If both the above conditions hold, the connection is put into the high
121-priority queue and its tickets value is decremented. Otherwise the
122-connection is put into the common queue with the initial tickets value
123-specified with this option.
124-
125-Each time the thread pool looks for a new connection to process, it
126-first checks the high priority queue, and picks connections from the
127-common queue only when the high priority one is empty.
128-
129-The idea is to minimize the number of open transactions in the
130-server. In many cases it is beneficial to give short-running
131-transactions a chance to commit faster and thus release server resources
132-and locks without waiting in the same queue with other connections that
133-are about to start a new transaction, or those that have run out of
134-their high priority tickets.
135-
136-With the default value of 0, all connections are always put into the
137-common queue, i.e. no priority scheduling is used as in the original
138-implementation in |MariaDB|. The higher is the value, the more chances
139-each transaction gets to enter the high priority queue and commit before
140-it is put in the common queue.
141-
142 Status Variables
143 =====================
144
145
146=== added file 'doc/source/release-notes/Percona-Server-5.5.30-30.2.rst'
147--- doc/source/release-notes/Percona-Server-5.5.30-30.2.rst 1970-01-01 00:00:00 +0000
148+++ doc/source/release-notes/Percona-Server-5.5.30-30.2.rst 2013-04-10 13:09:24 +0000
149@@ -0,0 +1,73 @@
150+.. rn:: 5.5.30-30.2
151+
152+==============================
153+ |Percona Server| 5.5.30-30.2
154+==============================
155+
156+Percona is glad to announce the release of |Percona Server| 5.5.30-30.2 on April 10th, 2013 (Downloads are available `here <http://www.percona.com/downloads/Percona-Server-5.5/Percona-Server-5.5.30-30.2/>`_ and from the `Percona Software Repositories <http://www.percona.com/docs/wiki/repositories:start>`_).
157+
158+Based on `MySQL 5.5.30 <http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-30.html>`_, including all the bug fixes in it, |Percona Server| 5.5.30-30.2 is now the current stable release in the 5.5 series. All of |Percona|'s software is open-source and free, all the details of the release can be found in the `5.5.30-30.2 milestone at Launchpad <https://launchpad.net/percona-server/+milestone/5.5.30-30.2>`_.
159+
160+New Features
161+============
162+
163+ |Percona Server| has implemented priority connection scheduling for the :ref:`threadpool`. (*Alexey Kopytov*)
164+
165+ |Percona Server| will now be shipped with the ``libjemalloc`` library. Benchmark showing the impact of memory allocators on |MySQL| performance can be found in this `blogpost <http://www.mysqlperformanceblog.com/2012/07/05/impact-of-memory-allocators-on-mysql-performance/>`_. (*Ignacio Nin*)
166+
167+ This release of |Percona Server| has fixed a number of performance bugs. (*Alexey Kopytov*)
168+
169+ :ref:`innodb_lazy_drop_table_page` has been removed and its controlling variable :variable:`innodb_lazy_drop_table` has been deprecated. Feature has been removed because the upstream ``DROP TABLE`` implementation has been improved. (*Laurynas Biveinis*)
170+
171+Bug Fixes
172+=========
173+
174+ Due to parse error in the :file:`percona-server.spec` |Percona Server| rpm packages couldn't be built on *RHEL* 5 and *CentOS* 5. Bug fixed :bug:`1144777` (*Ignacio Nin*).
175+
176+ When **mysqldump** was used with :option:`--innodb-optimize-keys` option it produced invalid SQL for cases when there was an explicitly named foreign key constraint which implied an implicit secondary index with the same name. Fixed by detecting such cases and omitting the corresponding secondary keys from deferred key creation optimization. Bug fixed :bug:`1081016` (*Alexey Kopytov*).
177+
178+ |Percona Server| was built with YaSSL which could cause some of the programs that use it to crash. Fixed by building packages with OpenSSL support rather than the bundled YaSSL library. Bug fixed :bug:`1104977` (*Ignacio Nin*).
179+
180+ Running a DDL statement while :variable:`innodb_lazy_drop_table` was enabled could cause assertion failure. Bugs fixed :bug:`1086227` and :bug:`1128848` (*Laurynas Biveinis*).
181+
182+ Fixed yum dependencies that were causing conflicts in ``CentOS`` 6.3 during installation. Bugs fixed :bug:`1031427` and :bug:`1051874` (*Ignacio Nin*).
183+
184+ The log tracker thread was unaware of the situation when the oldest untracked log records are overwritten by the new log data. In some corner cases this could lead to assertion errors in the log parser or bad changed page data. Bug fixed :bug:`1108613` (*Laurynas Biveinis*).
185+
186+ Ported a fix from *MariaDB* for the upstream bug :mysqlbug:`63144`. ``CREATE TABLE`` or ``CREATE TABLE IF NOT EXISTS`` statements on an existing table could wait on a metadata lock instead of failing or returning immediately if there is a transaction that executed a query which opened that table. Bug fixed :bug:`1127008` (*Sergei Glushchenko*).
187+
188+ Fix for bug :bug:`1070856` introduced a regression in |Percona Server| :rn:`5.5.28-29.3` which could cause a server to hang when binary log is enabled. Bug fixed :bug:`1162085` (*Alexey Kopytov*).
189+
190+ Fixed upstream bug :mysqlbug:`49169` by avoiding the ``malloc`` call in the ``read_view_create_low()`` in most cases. This significantly improves |InnoDB| scalability on read-only workloads, especially when the default glibc memory allocator is used. Bug fixed :bug:`1131187` (*Alexey Kopytov*).
191+
192+ Removed ``trx_list`` scan in ``read_view_open_now()`` which is another problem originally reported as upstream bug :mysqlbug:`49169`. This also provides much better scalability in |InnoDB| high-concurrent workloads. Bugs fixed :bug:`1131189` (*Alexey Kopytov*).
193+
194+ In the event that a slave was disconnected from the master, under certain conditions, upon reconnect, it would report that it received a packet larger than the :variable:`slave_max_allowed_packet` variable. Bug fixed :bug:`1135097` (*George Ormond Lorch III*).
195+
196+ Fixed the upstream bug :mysqlbug:`62578` which caused |MySQL| client to abort the connections on terminal resize. Bug fixed :bug:`925343` (*Sergei Glushchenko*).
197+
198+ |Percona Server| would re-create the test database when using ``rpm`` on server upgrade, even if the database was previously removed. Bug fixed :bug:`710799` (*Alexey Bychko*).
199+
200+ Debian packages included the old version of **innotop**. Fixed by removing **innotop** and its ``InnoDBParser`` Perl package from source and Debian installation. Bug fixed :bug:`1032139` (*Alexey Bychko*).
201+
202+ UDF/configure.ac was incompatible with ``automake`` 1.12. Bug fixed :bug:`1099387` (*Alexey Bychko*).
203+
204+ Reduced the overhead from `innodb_pass_corrupt_table`` value checks by optimizing them for better CPU branch prediction. Bug fixed :bug:`1125248` (*Alexey Kopytov*).
205+
206+ ``dialog.so`` used by the :ref:`pam_plugin` couldn't be loaded with Perl and Python clients when :variable:`plugin-dir` option was set in the ``[client]`` section of the :file:`my.cnf`. Bug fixed :bug:`1155859` (*Sergei Glushchenko*).
207+
208+ Fixed the upstream bug :mysqlbug:`68845` which could unnecessarily increase contention on ``log_sys->mutex`` in write-intensive workloads. Bug fixed :bug:`1163439` (*Alexey Kopytov*).
209+
210+ Ported back from the upstream |MySQL| 5.6 the fix for unnecessary ``log_flush_order_mutex`` acquisition. Bug fixed :bug:`1163262` (*Alexey Kopytov*).
211+
212+ When **mysqldump** was used with :option:`--innodb-optimize-keys` and :option:`--no-data` options, all secondary key definitions would be lost. Bug fixed :bug:`989253` (*Alexey Kopytov*).
213+
214+ Warning about the *Percona Toolkit* UDFs was omitted when installing from Percona's *Debian* repositories. Bug fixed :bug:`1015506` (*Alexey Bychko*).
215+
216+ |Percona Server| was missing help texts in the |MySQL| client because the help tables were missing. Bug fixed :bug:`1041981` (*Alexey Bychko*).
217+
218+ Fixed the upstream bug :mysqlbug:`68197` that caused |InnoDB| to misclassify internal read operations as synchronous when they were actually asynchronous when :ref:`threadpool` feature was used. Bug fixed :bug:`1107539` (*Sergei Glushchenko*).
219+
220+ Suboptimal code for :ref:`user_stats` feature has been optimized to make sure no additional work is done when :variable:`userstat` is disabled. Bug fixed :bug:`1128066` (*Alexey Kopytov*).
221+
222+Other bug fixes: bug fixed :bug:`1146621` (*Laurynas Biveinis*), bug fixed :bug:`1050536` (*Alexey Bychko*), bug fixed :bug:`1144059` (*Roel Van de Paar*), bug fixed :bug:`1154962` (*Hrvoje Matijakovic*), bug fixed :bug:`1154959` (*Hrvoje Matijakovic*), bug fixed :bug:`1154957` (*Hrvoje Matijakovic*), bug fixed :bug:`1154954` (*Hrvoje Matijakovic*).
223
224=== modified file 'doc/source/release-notes/release-notes_index.rst'
225--- doc/source/release-notes/release-notes_index.rst 2013-03-06 06:41:38 +0000
226+++ doc/source/release-notes/release-notes_index.rst 2013-04-10 13:09:24 +0000
227@@ -6,6 +6,7 @@
228 :maxdepth: 1
229 :glob:
230
231+ Percona-Server-5.5.30-30.2
232 Percona-Server-5.5.30-30.1
233 Percona-Server-5.5.29-30.0
234 Percona-Server-5.5.29-29.4
235
236=== modified file 'doc/source/upstream-bug-fixes.rst'
237--- doc/source/upstream-bug-fixes.rst 2013-04-09 21:37:02 +0000
238+++ doc/source/upstream-bug-fixes.rst 2013-04-10 13:09:24 +0000
239@@ -5,27 +5,57 @@
240 =============================================================
241
242 +-------------------------------------------------------------------------------------------------------------+
243+|:Upstream bug: :mysqlbug:`68197` - InnoDB reports that it's going to wait for I/O but the I/O is async |
244+|:Launchpad bug: :bug:`1107539` |
245+|:Upstream state: Closed |
246+|:Fix Released: :rn:`5.5.30-30.2` |
247+|:Upstream fix: 5.5.31 |
248++-------------------------------------------------------------------------------------------------------------+
249+|:Upstream bug: :mysqlbug:`68845` - Unnecessary log_sys->mutex reacquisition in mtr_log_reserve_and_write() |
250+|:Launchpad bug: :bug:`1163439` |
251+|:Upstream state: Open (checked on 2013-04-10) |
252+|:Fix Released: :rn:`5.5.30-30.2` |
253+|:Upstream fix: N/A |
254++-------------------------------------------------------------------------------------------------------------+
255+|:Upstream bug: :mysqlbug:`62578` - mysql client aborts connection on terminal resize |
256+|:Launchpad bug: :bug:`925343` |
257+|:Upstream state: Verified (checked on 2013-04-10) |
258+|:Fix Released: :rn:`5.5.30-30.2` |
259+|:Upstream fix: N/A |
260++-------------------------------------------------------------------------------------------------------------+
261+|:Upstream bug: :mysqlbug:`49169` - read_view_open_now is inefficient with many concurrent sessions |
262+|:Launchpad bug: :bug:`1131187` and :bug:`1131189` |
263+|:Upstream state: Closed |
264+|:Fix Released: :rn:`5.5.30-30.2` |
265+|:Upstream fix: N/A |
266++-------------------------------------------------------------------------------------------------------------+
267+|:Upstream bug: :mysqlbug:`63144` - CREATE TABLE IF NOT EXISTS metadata lock is too restrictive |
268+|:Launchpad bug: :bug:`1127008` |
269+|:Upstream state: Verified (checked on 2013-04-10) |
270+|:Fix Released: :rn:`5.5.30-30.2` |
271+|:Upstream fix: N/A |
272++-------------------------------------------------------------------------------------------------------------+
273 |:Upstream bug: :mysqlbug:`68477` - Suboptimal code in skip_trailing_space() |
274 |:Launchpad bug: :bug:`1132351` |
275-|:Upstream state: Verified (checked on 2013-03-05) |
276+|:Upstream state: Verified (checked on 2013-04-10) |
277 |:Fix Released: :rn:`5.5.30-30.1` |
278 |:Upstream fix: N/A |
279 +-------------------------------------------------------------------------------------------------------------+
280 |:Upstream bug: :mysqlbug:`68476` - Suboptimal code in my_strnxfrm_simple() |
281 |:Launchpad bug: :bug:`1132350` |
282-|:Upstream state: Verified (checked on 2013-03-05) |
283+|:Upstream state: Verified (checked on 2013-04-10) |
284 |:Fix Released: :rn:`5.5.30-30.1` |
285 |:Upstream fix: N/A |
286 +-------------------------------------------------------------------------------------------------------------+
287 |:Upstream bug: :mysqlbug:`68116` - InnoDB monitor may hit an assertion error in buf_page_get_gen in debug ...|
288 |:Launchpad bug: :bug:`1100178` |
289-|:Upstream state: Analyzing (checked on 2013-02-21) |
290+|:Upstream state: Analyzing (checked on 2013-04-10) |
291 |:Fix Released: :rn:`5.5.29-30.0` |
292 |:Upstream fix: N/A |
293 +-------------------------------------------------------------------------------------------------------------+
294 |:Upstream bug: :mysqlbug:`67504` - Duplicate error in replication with slave triggers and auto increment |
295 |:Launchpad bug: :bug:`1068210` |
296-|:Upstream state: Verified (checked on 2013-02-21) |
297+|:Upstream state: Verified (checked on 2013-04-10) |
298 |:Fix Released: :rn:`5.5.29-30.0` |
299 |:Upstream fix: N/A |
300 +-------------------------------------------------------------------------------------------------------------+
301@@ -61,7 +91,7 @@
302 +-------------------------------------------------------------------------------------------------------------+
303 |:Upstream bug: :mysqlbug:`66237` - Temporary files created by binary log cache are not purged after transa...|
304 |:Launchpad bug: :bug:`1070856` |
305-|:Upstream state: Verified (checked on 2013-02-21) |
306+|:Upstream state: Verified (checked on 2013-04-10) |
307 |:Fix Released: :rn:`5.5.28-29.3` |
308 |:Upstream fix: N/A |
309 +-------------------------------------------------------------------------------------------------------------+
310@@ -85,55 +115,55 @@
311 +-------------------------------------------------------------------------------------------------------------+
312 |:Upstream bug: :mysqlbug:`62856` - Check for "stack overrun" doesn't work with gcc-4.6, server crashes |
313 |:Launchpad bug: :bug:`1042517` |
314-|:Upstream state: Verified (checked on 2013-02-21) |
315+|:Upstream state: Closed |
316 |:Fix Released: :rn:`5.5.28-29.1` |
317 |:Upstream fix: N/A |
318 +-------------------------------------------------------------------------------------------------------------+
319 |:Upstream bug: :mysqlbug:`61180` - korr/store macros in my_global.h assume the argument to be a char pointer |
320 |:Launchpad bug: :bug:`1042517` |
321-|:Upstream state: Verified (checked on 2013-02-21) |
322+|:Upstream state: Verified (checked on 2013-04-10) |
323 |:Fix Released: :rn:`5.5.27-29.0` |
324 |:Upstream fix: N/A |
325 +-------------------------------------------------------------------------------------------------------------+
326 |:Upstream bug: :mysqlbug:`61179` - Unoptimized versions of korr/store macros in my_global.h are used on ... |
327 |:Launchpad bug: :bug:`1042517` |
328-|:Upstream state: Verified (checked on 2013-02-21) |
329+|:Upstream state: Verified (checked on 2013-04-10) |
330 |:Fix Released: :rn:`5.5.27-29.0` |
331 |:Upstream fix: N/A |
332 +-------------------------------------------------------------------------------------------------------------+
333 |:Upstream bug: :mysqlbug:`61178` - Incorrect implementation of intersect(ulonglong) in non-optimized Bitmap..|
334 |:Launchpad bug: :bug:`1042517` |
335-|:Upstream state: Verified (checked on 2013-02-21) |
336+|:Upstream state: Verified (checked on 2013-04-10) |
337 |:Fix Released: :rn:`5.5.27-29.0` |
338 |:Upstream fix: N/A |
339 +-------------------------------------------------------------------------------------------------------------+
340 |:Upstream bug: :mysqlbug:`54127` - mysqld segfaults when built using --with-max-indexes=128 |
341 |:Launchpad bug: :bug:`1042517` |
342-|:Upstream state: Verified (checked on 2013-02-21) |
343+|:Upstream state: Verified (checked on 2013-04-10) |
344 |:Fix Released: :rn:`5.5.27-29.0` |
345 |:Upstream fix: N/A |
346 +-------------------------------------------------------------------------------------------------------------+
347 |:Upstream bug: :mysqlbug:`64800` - mysqldump with --include-master-host-port putting quotes around port no. |
348 |:Launchpad bug: :bug:`1013432` |
349-|:Upstream state: Verified (checked on 2013-02-21) |
350+|:Upstream state: Verified (checked on 2013-04-10) |
351 |:Fix Released: :rn:`5.5.27-28.0` |
352 |:Upstream fix: N/A |
353 +-------------------------------------------------------------------------------------------------------------+
354 |:Upstream bug: :mysqlbug:`66301` - INSERT ... ON DUPLICATE KEY UPDATE + innodb_autoinc_lock_mode=1 is broken |
355 |:Launchpad bug: :bug:`1035225` |
356-|:Upstream state: Verified (checked on 2013-02-21) |
357+|:Upstream state: Verified (checked on 2013-04-10) |
358 |:Fix Released: :rn:`5.5.27-28.0` |
359 |:Upstream fix: N/A |
360 +-------------------------------------------------------------------------------------------------------------+
361 |:Upstream bug: :mysqlbug:`60743` - typo in cmake/dtrace.cmake |
362 |:Launchpad bug: :bug:`1013455` |
363-|:Upstream state: Verified (checked on 2013-02-21) |
364+|:Upstream state: Verified (checked on 2013-04-10) |
365 |:Fix Released: :rn:`5.5.25a-27.1` |
366 |:Upstream fix: N/A |
367 +-------------------------------------------------------------------------------------------------------------+
368 |:Upstream bug: :mysqlbug:`64663` - Segfault when adding indexes to InnoDB temporary tables |
369 |:Launchpad bug: :bug:`999147` |
370-|:Upstream state: Verified (checked on 2013-02-21) |
371+|:Upstream state: Verified (checked on 2013-04-10) |
372 |:Fix Released: :rn:`5.5.24-26.0` |
373 |:Upstream fix: N/A |
374 +-------------------------------------------------------------------------------------------------------------+
375@@ -151,9 +181,9 @@
376 +-------------------------------------------------------------------------------------------------------------+
377 |:Upstream bug: :mysqlbug:`64432` - Bug :mysqlbug:`54330` (Broken fast index creation) was never fixed in 5.5 |
378 |:Launchpad bug: :bug:`939485` |
379-|:Upstream state: Documenting (checked on 2013-02-21) |
380+|:Upstream state: Closed |
381 |:Fix Released: :rn:`5.5.21-25.0` |
382-|:Upstream fix: N/A |
383+|:Upstream fix: 5.5.30 |
384 +-------------------------------------------------------------------------------------------------------------+
385 |:Upstream bug: :mysqlbug:`49336` - mysqlbinlog does not accept input from stdin when stdin is a pipe |
386 |:Launchpad bug: :bug:`933969` |
387@@ -175,7 +205,7 @@
388 +-------------------------------------------------------------------------------------------------------------+
389 |:Upstream bug: :mysqlbug:`62516` - Fast index creation does not update index statistics |
390 |:Launchpad bug: :bug:`857590` |
391-|:Upstream state: Verified (checked on 2013-02-21) |
392+|:Upstream state: Verified (checked on 2013-04-10) |
393 |:Fix Released: :rn:`5.5.16-22.0` |
394 |:Upstream fix: N/A |
395 +-------------------------------------------------------------------------------------------------------------+
396@@ -187,7 +217,7 @@
397 +-------------------------------------------------------------------------------------------------------------+
398 |:Upstream bug: :mysqlbug:`61595` - mysql-test/include/wait_for_slave_param.inc timeout logic is incorrect |
399 |:Launchpad bug: :bug:`800035` |
400-|:Upstream state: Verified (checked on 2013-02-21) |
401+|:Upstream state: Verified (checked on 2013-04-10) |
402 |:Fix Released: :rn:`5.5.13-20.4` |
403 |:Upstream fix: N/A |
404 +-------------------------------------------------------------------------------------------------------------+

Subscribers

People subscribed via source and target branches