memory-table

Mysql: what to do when memory tables reach max_heap_table_size?

ⅰ亾dé卋堺 提交于 2019-12-11 06:45:08
问题 I'm using a mysql memory table as a way to cache data rows which are read several times. I chose this alternative because I'm not able to use xcache or memcache in my solution. After reading the mysql manual and forum about this topic I have concluded that an error will be raised when the table reaches its maximum memory size. I want to know if there is a way to catch this error in order to truncate the table and free the memory. I don't want to raise the limit of memory that can be used, I

Indexing every column in a table

蓝咒 提交于 2019-11-29 06:10:41
I have a couple of questions regarding MySQL indexing: 1) Is there any speed increase when indexing a table stored in memory? 2) When searching my table I match on column field, would indexing every column defeat the purpose of an index? Many thanks. Fuu Indexing any table, either memory or file system based, will speed up queries that select or sort results based on that column. This is because the index works like a tree structure and the search distance depends on the depth of the tree, which increases a lot slower than the row count of the column (logarithmic). Indexing every column does

Indexing every column in a table

可紊 提交于 2019-11-27 23:42:07
问题 I have a couple of questions regarding MySQL indexing: 1) Is there any speed increase when indexing a table stored in memory? 2) When searching my table I match on column field, would indexing every column defeat the purpose of an index? Many thanks. 回答1: Indexing any table, either memory or file system based, will speed up queries that select or sort results based on that column. This is because the index works like a tree structure and the search distance depends on the depth of the tree,