MySQL Bugs: #54505: InnoDB documentation: glossary is empty

Bug #54505	InnoDB documentation: glossary is empty
Submitted:	15 Jun 2010 7:00	Modified:	27 Dec 2010 12:54
Reporter:	Daniël van Eeden	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S4 (Feature request)
Version:		OS:	Any
Assigned to:	Valeriy Kravchuk	CPU Architecture:	Any
Tags:	Contribution, documentation, InnoDB plugin

Description:
The glossary in the documentation is empty
http://www.innodb.com/doc/innodb_plugin-1.0/glossary.html

How to repeat:
Read docs

Suggested fix:
Add at least the following glossary:
- Server: The database server instance. This is the mysqld process and not the physical system on which it is running.
- Tablespace: A file containing one or more tables
- System Tablespace: The ibdata* files.
- INFORMATION_SCHEMA: Information in the database about the databases which can be accessed like any other MySQL database.
- spin loop: a process which is active without doing something useful.
- spin lock: constantly checking if a lock is released.
- Schema: A database and the tables in that database
- LRU: Least-Recently-Used
- Page: A part of the datafile of 16K uncomressed. When using compression the size can be 1K, 2K, 4K or 8K.
- Storage Engine: The backend part for MySQL which decides how a table is stored on disk or memory. Examples are: InnoDB, MyISAM and NDB.
- Hash Index: An ondemand index which makes data access faster if the table fits almost entirely in main memory.
- Dirty Pages: Pages which are not yet written to disk
- Dynamic Variable: A variable which can be changed without restarting the MySQL server.
- Mutex: Mutual exclusion

Thank you for the documentation request.

The glossary for 1.1 is not empty.
http://dev.mysql.com/doc/innodb/1.1/en/glossary.html

The InnoDB 1.0 docs on docs.mysql.com doesn't seem to contain a glossary.

Should we consider this fixed?

Indeed, looks fixed by our documentation team for 1.1.