Bug #20071 LOGFILE_GROUP_NAME in on-line docs needs to be corrected

Submitted: 25 May 2006 18:27 Modified: 2 Jun 2006 5:40
Reporter: Jonathan Miller Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:5.1.12 OS:Linux (Linux 32 Bit OS)
Assigned to: Jon Stephens CPU Architecture:Any

[25 May 2006 18:27] Jonathan Miller 
Description:

 For an UNDO logfile, LOGFILE_GROUP_NAME gives the name of the logfile group to which the logfile belongs. For a datafile, this column is empty.

See below. Seems to have a LOGFILE_GROUP_NAME for a datafile to me.

*************************** 5. row ***************************
           FILE_NAME: datafile.dat
           FILE_TYPE: DATAFILE
     TABLESPACE_NAME: ts2
  LOGFILE_GROUP_NAME: lg2
LOGFILE_GROUP_NUMBER: 0
        FREE_EXTENTS: 12
       TOTAL_EXTENTS: 12
        INITIAL_SIZE: 12582912
        MAXIMUM_SIZE: 12582912
              STATUS: NORMAL
               EXTRA: CLUSTER_NODE=2

How to repeat:
N/A

Suggested fix:
Correct on-line docs
[25 May 2006 18:28] Jonathan Miller 
http://dev.mysql.com/doc/refman/5.1/en/files-table.html
[25 May 2006 18:30] Jonathan Miller 
For a MySQL Cluster Disk Data logfile or datafile, the value of the ENGINE column is always NDB.
actually
 ENGINE: ndbcluster
[2 Jun 2006 5:40] Jon Stephens 
Thank you for your bug report. This issue has been addressed in the
documentation. The updated documentation will appear on our website
shortly, and will be included in the next release of the relevant
product(s).

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.054 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.