StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
10010608
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2012-04-04T11:57:55.860
FavoriteCount
0
LastActivityDate
2012-04-04T11:57:55.860
LastEditDate
LastEditorUserId
0
OwnerUserId
356446
ParentId
9930556
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Basically, you are doing an <code>OPTIMIZE</code> on the table. For InnoDB tables, <code>OPTIMIZE</code> is mapped to <code>ALTER TABLE</code>. Quoting from the Mysql manual : <blockquote> For InnoDB tables, OPTIMIZE TABLE is mapped to ALTER TABLE, which rebuilds the table to update index statistics and free unused space in the clustered index. </blockquote> When deleting 1/2 a table, an <code>OPTIMIZE</code> after is a really good idea. I would make a suggestion for improving performance. Seeing that you support in your configuration the new file format <code>BARRACUDA</code> you should use it. Enabling it is really easy, just add in your <code>my.cnf</code> : <pre><code>innodb_file_format=Barracuda </code></pre> Restart the server and then alter your table to use the new available <code>ROW_FORMAT = COMPRESSED</code> : <pre><code>ALTER TABLE x ROW_FORMAT=COMPRESSED; </code></pre> From personal experience, when using the compressed row format, table size has reduced to half and it a significant positive impact on performance as well. For more details try going throug : <a href="http://dev.mysql.com/doc/refman/5.5/en/innodb-compression-usage.html" rel="nofollow">http://dev.mysql.com/doc/refman/5.5/en/innodb-compression-usage.html</a> <a href="http://www.mysqlperformanceblog.com/2008/04/23/testing-innodb-barracuda-format-with-compression/" rel="nofollow">http://www.mysqlperformanceblog.com/2008/04/23/testing-innodb-barracuda-format-with-compression/</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POInnoDB table optimization w/o locking table
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. UScapi
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. COAre there downsides to using the new file format or row compression?
 singulars
 PostPostId
 PO
 UserUserId
 USJeremy
2. COThere should be a minor increase in CPU usage, but all the tests I've seen indicate that there is no downside. The old format "Antelope" is kept as default mainly for compatibility with older MySQL versions. The new Barracuda file format will most likely become the default in the next major MySQL release.
 singulars
 PostPostId
 PO
 UserUserId
 UScapi

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.