Bug #29263 disabled storage engines omitted in SHOW ENGINES

Description:
 [15 Jun 13:10] Jon Stephens

This is from a fresh pull, build using compile-amd64-debug-max:

mysql> SELECT VERSION();
+-------------------+
| VERSION()         |
+-------------------+
| 5.1.20-beta-debug |
+-------------------+
1 row in set (0.00 sec)

mysql> SHOW ENGINES;
+------------+---------+----------------------------------------------------------------+-
-------------+-----+------------+
| Engine     | Support | Comment                                                        |
Transactions | XA  | Savepoints |
+------------+---------+----------------------------------------------------------------+-
-------------+-----+------------+
| InnoDB     | YES     | Supports transactions, row-level locking, and foreign keys     |
YES          | YES | YES        |
| MRG_MYISAM | YES     | Collection of identical MyISAM tables                          |
NO           | NO  | NO         |
| BLACKHOLE  | YES     | /dev/null storage engine (anything you write to it disappears) |
NO           | NO  | NO         |
| CSV        | YES     | CSV storage engine                                             |
NO           | NO  | NO         |
| MEMORY     | YES     | Hash based, stored in memory, useful for temporary tables      |
NO           | NO  | NO         |
| FEDERATED  | YES     | Federated MySQL storage engine                                 |
YES          | NO  | NO         |
| ARCHIVE    | YES     | Archive storage engine                                         |
NO           | NO  | NO         |
| MyISAM     | DEFAULT | Default engine as of MySQL 3.23 with great performance         |
NO           | NO  | NO         |
+------------+---------+----------------------------------------------------------------+-
-------------+-----+------------+
8 rows in set (0.00 sec)

mysql> SELECT * FROM INFORMATION_SCHEMA.ENGINES;
+------------+---------+----------------------------------------------------------------+-
-------------+-----+------------+
| ENGINE     | SUPPORT | COMMENT                                                        |
TRANSACTIONS | XA  | SAVEPOINTS |
+------------+---------+----------------------------------------------------------------+-
-------------+-----+------------+
| InnoDB     | YES     | Supports transactions, row-level locking, and foreign keys     |
YES          | YES | YES        |
| MRG_MYISAM | YES     | Collection of identical MyISAM tables                          |
NO           | NO  | NO         |
| BLACKHOLE  | YES     | /dev/null storage engine (anything you write to it disappears) |
NO           | NO  | NO         |
| CSV        | YES     | CSV storage engine                                             |
NO           | NO  | NO         |
| MEMORY     | YES     | Hash based, stored in memory, useful for temporary tables      |
NO           | NO  | NO         |
| FEDERATED  | YES     | Federated MySQL storage engine                                 |
YES          | NO  | NO         |
| ARCHIVE    | YES     | Archive storage engine                                         |
NO           | NO  | NO         |
| MyISAM     | DEFAULT | Default engine as of MySQL 3.23 with great performance         |
NO           | NO  | NO         |
+------------+---------+----------------------------------------------------------------+-
-------------+-----+------------+
8 rows in set (0.00 sec)

I have verified that all the NDB executables were built, but where are the columns for
NDB? They should be present, and have the value DISABLED.

Were the server built without NDB support at all, then the columns should also be there,
but have the value NO.

See http://dev.mysql.com/doc/refman/5.1/en/show-engines.html

How to repeat:
see http://bugs.mysql.com/bug.php?id=27684

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/33803

ChangeSet@1.2578, 2007-09-06 17:02:37+05:00, gluh@mysql.com +4 -0
  Bug#29263 disabled storage engines omitted in SHOW ENGINES
  added filling of 'engines' table with disabled builtin plugins

See also Bug #36068

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/56176

2759 Sergey Glukhov	2008-10-14
      Bug#29263 disabled storage engines omitted in SHOW ENGINES
      Static disabled plugins|engines and dynamic plugins which installed but disabled
      are not visible in I_S PLUGINS|ENGINES tables because they are not stored into
      global plugin array.
      The fix: add such plugins|engines to plugin array with PLUGIN_IS_DISABLED status.
      I_S.ENGINES 'Transactions', 'XA', 'Savepoints' fields have NULL value in this case.

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/56441

2759 Sergey Glukhov	2008-10-17
      Bug#29263 disabled storage engines omitted in SHOW ENGINES
      Static disabled plugins|engines and dynamic plugins which installed but disabled
      are not visible in I_S PLUGINS|ENGINES tables because they are not stored into
      global plugin array.
      The fix: add such plugins|engines to plugin array with PLUGIN_IS_DISABLED status.
      I_S.ENGINES 'Transactions', 'XA', 'Savepoints' fields have NULL value in this case.

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/61876

2740 Sergey Glukhov	2008-12-17
      Bug#29263 disabled storage engines omitted in SHOW ENGINES
      Static disabled plugins|engines and dynamic plugins which installed but disabled
      are not visible in I_S PLUGINS|ENGINES tables because they are not stored into
      global plugin array.
      The fix: add such plugins|engines to plugin array with PLUGIN_IS_DISABLED status.
      I_S.ENGINES 'Transactions', 'XA', 'Savepoints' fields have NULL value in this case.

Pushed into 5.1.31 (revid:joro@sun.com-20090115053147-tx1oapthnzgvs1ro) (version source revid:azundris@mysql.com-20081230114838-cn52tu180wcrvh0h) (merge vers: 5.1.31) (pib:6)

Pushed into 5.1.31-ndb-6.2.17 (revid:tomas.ulin@sun.com-20090119095303-uwwvxiibtr38djii) (version source revid:tomas.ulin@sun.com-20090115073240-1wanl85vlvw2she1) (merge vers: 5.1.31-ndb-6.2.17) (pib:6)

Pushed into 5.1.31-ndb-6.3.21 (revid:tomas.ulin@sun.com-20090119104956-guxz190n2kh31fxl) (version source revid:tomas.ulin@sun.com-20090119104956-guxz190n2kh31fxl) (merge vers: 5.1.31-ndb-6.3.21) (pib:6)

Pushed into 5.1.31-ndb-6.4.1 (revid:tomas.ulin@sun.com-20090119144033-4aylstx5czzz88i5) (version source revid:tomas.ulin@sun.com-20090119144033-4aylstx5czzz88i5) (merge vers: 5.1.31-ndb-6.4.1) (pib:6)

Pushed into 6.0.10-alpha (revid:joro@sun.com-20090119171328-2hemf2ndc1dxl0et) (version source revid:azundris@mysql.com-20081230114916-c290n83z25wkt6e4) (merge vers: 6.0.9-alpha) (pib:6)

Noted in 5.1.31, 6.0.10 changelog.

Static storage engines and plugins that were disabled and dynamic
plugins that were instaled but disabled were not listed in the
INFORMATION_SCHEMA appropriate PLUGINS or ENGINES table.

Note that the "repair" of this "problem" has led to another problem, one we consider more important than this one: "Dynamic plugin broken in 5.1.31" http://bugs.mysql.com/bug.php?id=42610.

Is there any solution to overcome the in built plugin..If so pl..post the solution for this issue...