# [EMAIL PROTECTED] / 2003-09-25 08:58:09 +0300:
From: Roman Neuhauser [EMAIL PROTECTED]
Also, is there a way to *measure* the fragmentation of a table?
If there is, how should the info be interpreted?
Sorry, no. But adding such a feature would be easy: just look at page
numbers, page
Roman,
- Alkuperäinen viesti -
Lähettäjä: Roman Neuhauser [EMAIL PROTECTED]
Vastaanottaja: Heikki Tuuri [EMAIL PROTECTED]
Kopio: [EMAIL PROTECTED]
Lähetetty: Friday, September 26, 2003 12:02 PM
Aihe: Re: innodb: storage requirements
# [EMAIL PROTECTED] / 2003-09-25 08:58:09 +0300
Roman,
- Original Message -
From: Roman Neuhauser [EMAIL PROTECTED]
To: Heikki Tuuri [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Wednesday, September 24, 2003 11:46 PM
Subject: Re: innodb: storage requirements
# [EMAIL PROTECTED] / 2003-09-24 17:41:29 +0300:
the row count in SHOW
tool for MySQL
- Original Message -
From: Roman Neuhauser [EMAIL PROTECTED]
Newsgroups: mailing.database.myodbc
Sent: Tuesday, September 23, 2003 6:38 PM
Subject: innodb: storage requirements
A simple question regarding storage allocated / reported by MySQL/InnoDB.
If BIGINT takes 8
# [EMAIL PROTECTED] / 2003-09-23 21:56:55 +0300:
From: Roman Neuhauser [EMAIL PROTECTED]
A simple question regarding storage allocated / reported by MySQL/InnoDB.
If BIGINT takes 8 bytes, and a table has exactly four BIGINT columns,
why is the reported avg. row length 148 bytes?
the table
PM
Subject: Re: innodb: storage requirements
# [EMAIL PROTECTED] / 2003-09-23 21:56:55 +0300:
From: Roman Neuhauser [EMAIL PROTECTED]
A simple question regarding storage allocated / reported by
MySQL/InnoDB.
If BIGINT takes 8 bytes, and a table has exactly four BIGINT columns,
why
# [EMAIL PROTECTED] / 2003-09-24 17:41:29 +0300:
the row count in SHOW TABLE STATUS is only an estimate based on 8
dives into the index tree.
ok.
You had a typical symptom of a fragmented table: space usage much bigger
than you would expect.
that doesn't answer my questions :)
A simple question regarding storage allocated / reported by MySQL/InnoDB.
If BIGINT takes 8 bytes, and a table has exactly four BIGINT columns,
why is the reported avg. row length 148 bytes?
mysql show table status from pmsystem2 like 'editor_competence_product'\G
*** 1.
