<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel>
        <title>MySQL Forums - Memory Storage Engine</title>
        <description>Forum for Memory Storage Engine.</description>
        <link>https://forums.mysql.com/list.php?92</link>
        <lastBuildDate>Wed, 20 May 2026 19:08:51 +0000</lastBuildDate>
        <generator>Phorum 5.2.23</generator>
        <item>
            <guid>https://forums.mysql.com/read.php?92,678644,678644#msg-678644</guid>
            <title>MySQL Inserting into Memory table triggers heavy disk activity (3 replies)</title>
            <link>https://forums.mysql.com/read.php?92,678644,678644#msg-678644</link>
            <description><![CDATA[ I am confused. I am creating a Memory table in my Schema:<br />
<br />
CREATE TABLE `memory_words` (<br />
  `word` varchar(128) NOT NULL ,<br />
  `COUNT` int NOT NULL,<br />
  PRIMARY KEY (`WORD`)<br />
) ENGINE=Memory DEFAULT CHARSET=utf8MB4;<br />
<br />
I am doing a lot of inserts into the table, for later statistics work. When monitoring the process, I see that my MySQL-server is starting a lot of writes to disk. Why? When using a Memory table, disk I/O should not be present?<br />
<br />
The SQL for inserting (upserting) is:<br />
<br />
INSERT INTO memory_words (word,COUNT) VALUES (_cleanstring,1) on duplicate key update COUNT=COUNT+1;<br />
<br />
The MySQL Server is hosted on a Local Docker-Server and is mine alone, so I can rule out that the disk I/O is triggered by other than me. The server has enough resources to hold the Memory-Table.<br />
<br />
Do I need to any config on table or server, to prevent disk I/O with Memory-tables?<br />
<br />
Thanks in advance Allan]]></description>
            <dc:creator>Allan Poulsen</dc:creator>
            <category>Memory Storage Engine</category>
            <pubDate>Mon, 21 Dec 2020 22:16:28 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?92,664954,664954#msg-664954</guid>
            <title>Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs (no replies)</title>
            <link>https://forums.mysql.com/read.php?92,664954,664954#msg-664954</link>
            <description><![CDATA[ Hello all,<br />
<br />
I am trying to create dynamic tables for excel file. Number of columns varies according to file uploading. When I tried to upload a file having 572 columns, MySQL server gave an error with an error code 1118 Row size too large. I figured that the query was too large so I tried creating table with 100 columns and add remaining columns with alter query. It works that way up to certain limit (196 columns). After that it still gives the same error. Although, it works fine on other machine. Is there any configuration setting that is needed to be changed? <br />
<br />
Query for create table is as given below,<br />
<br />
CREATE TABLE  `project11_module79` (<br />
  `insertdate` text,<br />
  `createdby` text,<br />
  `createddate` text,<br />
  `updatedby` text,<br />
  `updateddate` text,<br />
  `inserttimestamp` text,<br />
  `status` text,<br />
  `TestCase_ID_col` text,<br />
  `RunMode_col` text,<br />
  `DE1_col` text,<br />
  `PlanName_col` text,<br />
  `proposal_number_col` text,<br />
  `Description_col` text,<br />
  `Expected_Result_col` text,<br />
  `Status_col` text,<br />
  `Remarks_col` text,<br />
  `ScreenShotPath_col` text,<br />
  `ProposalIndividual_col` text,<br />
  `ChannelDetails_col` text,<br />
  `ProposalDetails_col` text,<br />
  `DetailsOfProposer_col` text,<br />
  `DetailsOfMinor_col` text,<br />
  `NominationDetails_col` text,<br />
  `BasicPlanDetails_col` text,<br />
  `LifeInsuranceDetails_col` text,<br />
  `FamilyHistoryOfLA_col` text,<br />
  `MedicalDetailsForLA_col` text,<br />
  `BankAccountDetailsOfLA_col` text,<br />
  `EinsuranceAccountDetails_col` text,<br />
  `PayerDetails_col` text,<br />
  `Form60_col` text,<br />
  `FatcaDetails_col` text,<br />
  `ProposalSubmition_col` text,<br />
  `P1_col` text,<br />
  `Prop_Category_col` text,<br />
  `P2_col` text,<br />
  `DisMarketing_col` text,<br />
  `DisMarketMode_col` text,<br />
  `P3_col` text,<br />
  `ProposalDate_col` text,<br />
  `Received_Date_col` text,<br />
  `Plan_Name_col` text,<br />
  `ExistSbiCust_col` text,<br />
  `Ext_SBI_Pol_Cust_col` text,<br />
  `AssignPolicy_col` text,<br />
  `PreferredLanguage_col` text,<br />
  `Proposal_Under_col` text,<br />
  `SimulProposalNo1_col` text,<br />
  `SimulProposalNo2_col` text,<br />
  `SimulProposalNo3_col` text,<br />
  `P4_col` text,<br />
  `Salutation_PA_col` text,<br />
  `PA_FirstName_col` text,<br />
  `PA_MiddleName_col` text,<br />
  `PA_LastName_col` text,<br />
  `PA_Gender_col` text,<br />
  `PA_DOB_col` text,<br />
  `PA_MaritalStatus_col` text,<br />
  `Maiden_FirstName_col` text,<br />
  `Maiden_MiddleName_col` text,<br />
  `Maiden_LastName_col` text,<br />
  `PA_Father_FN_col` text,<br />
  `PA_Father_MN_col` text,<br />
  `PA_Father_LN_col` text,<br />
  `PA_Mother_Name_col` text,<br />
  `PA_Spouse___Name_col` text,<br />
  `PA_Nationality_col` text,<br />
  `ProposerCountryResidence_col` text,<br />
  `Passport_Number_col` text,<br />
  `Passport_Issuance_Date_col` text,<br />
  `Passport_Valid_Upto_col` text,<br />
  `Age_Proof_col` text,<br />
  `Qualification_col` text,<br />
  `Identity_Proof_col` text,<br />
  `Identification_Number_col` text,<br />
  `Occupation_col` text,<br />
  `Company_Name_col` text,<br />
  `empDutyNature_col` text,<br />
  `empForceNumber_col` text,<br />
  `HazardOccupation_col` text,<br />
  `HazardDutyNature_col` text,<br />
  `PoliticallyExposed_col` text,<br />
  `Details_for_PEP_col` text,<br />
  `ConvictionHistory_col` text,<br />
  `CriminalDetails_col` text,<br />
  `SpouseInSBG_col` text,<br />
  `WorkinginSBG_col` text,<br />
  `Self_PF_Pension_Index_Employee_No_col` text,<br />
  `SpousePFPensionEmployeeNumber_col` text,<br />
  `Annual_Income_col` text,<br />
  `Source_Income_col` text,<br />
  `Incom_Prf_col` text,<br />
  `PAN_Num_col` text,<br />
  `AADHAR_Num_col` text,<br />
  `Submitted_Income_proof_col` text,<br />
  `Domicile_col` text,<br />
  `CmAddrTitle_col` text,<br />
  `CmAddrLine1_col` text,<br />
  `CmAddrLine2_col` text,<br />
  `CmAddrLine3_col` text,<br />
  `CmAddrPincode_col` text,<br />
  `CmAddrState_col` text,<br />
  `CmAddrCity_col` text,<br />
  `CmAddrDistrict_col` text,<br />
  `CmAddrProof_col` text,<br />
  `PaAddrsSameAsCm_col` text,<br />
  `PM_Add1_col` text,<br />
  `PM_Add2_col` text,<br />
  `PM_Add3_col` text,<br />
  `PM_Country_col` text,<br />
  `PM_Pincode_col` text,<br />
  `PM_AddrDistrict_col` text,<br />
  `PM_AddressProof_col` text,<br />
  `STD_Code_col` text,<br />
  `Home_Tel_No_col` text,<br />
  `OffSTDCode_col` text,<br />
  `Office_Tel_No_col` text,<br />
  `CountryCode1_col` text,<br />
  `MobileNumber1_col` text,<br />
  `CountryCode2_col` text,<br />
  `MobileNumber2_col` text,<br />
  `CountryCode3_col` text,<br />
  `MobileNumber3_col` text,<br />
  `Email_ID_Provided_col` text,<br />
  `Email_Id_col` text,<br />
  `LASameAsPR_col` text,<br />
  `P5_col` text,<br />
  `Salutation_LA_col` text,<br />
  `LA_FirstName_col` text,<br />
  `LA_MiddleName_col` text,<br />
  `LA_LastName_col` text,<br />
  `LA_Gender_col` text,<br />
  `LA_DOB_col` text,<br />
  `LA_MaritalStatus_col` text,<br />
  `LA_Father_FN_col` text,<br />
  `LA_Father_MN_col` text,<br />
  `LA_Father_LN_col` text,<br />
  `LA_Mother_Name_col` text,<br />
  `LA_Spouse_Name_col` text,<br />
  `MinorLArelationwithPR_col` text,<br />
  `LA_Nationality_col` text,<br />
  `LA_CountryResidence_col` text,<br />
  `LA_Passport_Number_col` text,<br />
  `LA_Passport_Issuance_Date_col` text,<br />
  `LA_Passport_Valid_Upto_col` text,<br />
  `LA_Age_Proof_col` text,<br />
  `LA_Qualification_col` text,<br />
  `LA_CmAddSameAsProp_col` text,<br />
  `LA_Domicile_col` text,<br />
  `LA_CmAddrTitle_col` text,<br />
  `LA_CmAddrLine1_col` text,<br />
  `LA_CmAddrLine2_col` text,<br />
  `LA_CmAddrLine3_col` text,<br />
  `LA_CmAddCountry_col` text,<br />
  `LA_CmAddrPincode_col` text,<br />
  `LA_CmAddrDistrict_col` text,<br />
  `LA_CmAddressProof_col` text,<br />
  `LA_PaAddsameAsCm_col` text,<br />
  `LA_PaAddrLine1_col` text,<br />
  `LA_PaAddrLine2_col` text,<br />
  `LA_PaAddrLine3_col` text,<br />
  `LA_PaAddCountry_col` text,<br />
  `LA_PaAddPincode_col` text,<br />
  `LA_PaAddrDistrict_col` text,<br />
  `LA_PaAddressProof_col` text,<br />
  `LA_STD_Code_col` text,<br />
  `LA_Home_Tel_No_col` text,<br />
  `LA_OffSTDCode_col` text,<br />
  `LA_Office_Tel_No_col` text,<br />
  `LA_CountryCode1_col` text,<br />
  `LA_MobileNumber1_col` text,<br />
  `LA_CountryCode2_col` text,<br />
  `LA_MobileNumber2_col` text,<br />
  `LA_CountryCode3_col` text,<br />
  `LA_MobileNumber3_col` text,<br />
  `LA_Email_ID_Provided_col` text,<br />
  `LA_Email_Id_col` text,<br />
  `P6_col` text,<br />
  `NM_Title_col` text,<br />
  `NM_FN_col` text,<br />
  `NM_MN_col` text,<br />
  `NM_LN_col` text,<br />
  `NM_DOB_col` text,<br />
  `NM_MaritalStatus_col` text,<br />
  `NM_Nationality_col` text,<br />
  `NMAgeProof_col` text,<br />
  `NM_Father_FN_col` text,<br />
  `NM_Father_MN_col` text,<br />
  `NM_Father_LN_col` text,<br />
  `NMRelationshipWithPR_col` text,<br />
  `NM_share_col` text,<br />
  `NMAddrssSameasPR_col` text,<br />
  `NM_Domicile_col` text,<br />
  `NM_Add1_col` text,<br />
  `NM_Add2_col` text,<br />
  `NM_Add3_col` text<br />
);<br />
<br />
This creates table with 196 columns but if I try to add one more column in same table for example, <br />
<br />
alter table project11_module79 add column newCol text;<br />
<br />
It gives an error saying,<br />
<br />
Error Code: 1118. Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs<br />
<br />
<br />
Thank you.]]></description>
            <dc:creator>Amey Kolapkar</dc:creator>
            <category>Memory Storage Engine</category>
            <pubDate>Tue, 13 Mar 2018 06:21:12 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?92,641017,641017#msg-641017</guid>
            <title>Memory Storage Engine executes Delete query at SQL Thread Start instaed of instance start (1 reply)</title>
            <link>https://forums.mysql.com/read.php?92,641017,641017#msg-641017</link>
            <description><![CDATA[ Hello,<br />
<br />
Want to check the behaviour of MYSQL 5.5.25 community edition, yesterday we noticed that due to some maintenance we have to restart the instance, which was having some tables with Memory Storage Engine. The instance came back fine but due to the maintenance we didn&#039;t start the slave or SQL Thread was down. We start this SQL Thread/slave after some 5 hours and then we noticed the Delete queries got fired for the Memory tables. <br />
<br />
<br />
I would like to check that Memory Storage Engine executes Delete query at SQL Thread Start instaed of instance start, is this a default behaviour??<br />
<br />
Jai<br />
<a href="mailto:&#106;&#97;&#105;&#112;&#115;&#104;&#97;&#114;&#109;&#97;&#64;&#121;&#97;&#104;&#111;&#111;&#46;&#99;&#111;&#46;&#105;&#110;">&#106;&#97;&#105;&#112;&#115;&#104;&#97;&#114;&#109;&#97;&#64;&#121;&#97;&#104;&#111;&#111;&#46;&#99;&#111;&#46;&#105;&#110;</a>]]></description>
            <dc:creator>JaiPrakash Sharma</dc:creator>
            <category>Memory Storage Engine</category>
            <pubDate>Fri, 01 Jan 2016 06:25:01 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?92,635909,635909#msg-635909</guid>
            <title>How to disable memory engine storage? (2 replies)</title>
            <link>https://forums.mysql.com/read.php?92,635909,635909#msg-635909</link>
            <description><![CDATA[ How to disable memory engine storage? I do not want to allow my users to use it at all.]]></description>
            <dc:creator>Andrew Vdovin</dc:creator>
            <category>Memory Storage Engine</category>
            <pubDate>Sun, 25 Oct 2015 19:24:26 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?92,626476,626476#msg-626476</guid>
            <title>memory tables swapped out? (2 replies)</title>
            <link>https://forums.mysql.com/read.php?92,626476,626476#msg-626476</link>
            <description><![CDATA[ As per the manual<br />
&quot;Data volume can fit entirely in memory without causing the operating<br />
system to swap out virtual memory pages&quot;<br />
<br />
Does this means, internally apply memlock? <br />
<br />
Or, will --memlock explicitly say not to swap the pages used for MEMORY tables.]]></description>
            <dc:creator>mahendra laxaman</dc:creator>
            <category>Memory Storage Engine</category>
            <pubDate>Thu, 08 Jan 2015 09:18:41 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?92,626401,626401#msg-626401</guid>
            <title>When using Memory Storage Join ON Clause would not work anymore (1 reply)</title>
            <link>https://forums.mysql.com/read.php?92,626401,626401#msg-626401</link>
            <description><![CDATA[ Hey<br />
<br />
I have a very curious error message.<br />
I use mySQL 5.5.28<br />
<br />
I use the following Select, which works alone:<br />
<br />
  SELECT DISTINCT <br />
  IF(i1.hst_code_grundglas IS NOT NULL, i1.hst_code_grundglas, <br />
     IF(i2.hst_code_grundglas IS NOT NULL, i2.hst_code_grundglas, <br />
        i3.hst_code_grundglas)) AS hst_code_grundglas,<br />
  iprooptions.phototrop,<br />
  iprooptions.hst_code_schicht<br />
FROM iprooptions<br />
  LEFT JOIN iprocombination i2<br />
    ON (iprooptions.hst_code_schicht = i2.hst_code_schicht2<br />
    AND i2.hst_code_grundglas =&#039;A9B&#039;<br />
    AND i2.hst_code_schicht2 &lt;&gt; &#039;******&#039;<br />
    AND i2.lieferbarkeit = 2 <br />
    AND iprooptions.manufacturer_code=i2.manufacturer_code)<br />
  LEFT JOIN iprocombination i1<br />
    ON (iprooptions.hst_code_schicht = i1.hst_code_schicht1<br />
    AND i1.hst_code_grundglas =&#039;A9B&#039;<br />
    AND i1.hst_code_schicht1 &lt;&gt; &#039;******&#039;<br />
    AND i1.lieferbarkeit = 2 <br />
    AND iprooptions.manufacturer_code=i1.manufacturer_code)<br />
  LEFT JOIN iprocombination i3<br />
    ON (iprooptions.hst_code_schicht = i3.hst_code_schicht3<br />
    AND i3.hst_code_grundglas =&#039;A9B&#039;<br />
    AND i3.hst_code_schicht3 &lt;&gt; &#039;******&#039;<br />
    AND i3.lieferbarkeit = 2 <br />
    AND iprooptions.manufacturer_code=i3.manufacturer_code)<br />
WHERE iprooptions.Farbe &gt; 0<br />
AND (i1.hst_code_schicht1 IS NOT NULL<br />
     OR i2.hst_code_schicht2 IS NOT NULL<br />
     OR i3.hst_code_schicht3 IS NOT NULL);<br />
<br />
Don&#039;t matter about the Select please.<br />
My Problem is, when I now surround this select with a Create Temporary Table tmp Enginge=Memory<br />
<br />
Then I get án error:<br />
1 Unknown column &#039;iprooptions.hst_code_schicht&#039; in &#039;on clause&#039; SQL2.sql 27 3 <br />
<br />
What is this?<br />
<br />
THX]]></description>
            <dc:creator>Harald Bacik</dc:creator>
            <category>Memory Storage Engine</category>
            <pubDate>Tue, 06 Jan 2015 17:46:30 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?92,624210,624210#msg-624210</guid>
            <title>Table Deleted Automatically Under No Replication (1 reply)</title>
            <link>https://forums.mysql.com/read.php?92,624210,624210#msg-624210</link>
            <description><![CDATA[ Hi community, <br />
Heap tables are deleted automatically under the following condition.<br />
<br />
0. MySQL 5.6.16 on Windows 7 <br />
1. No replication, single database.<br />
2. Setup collecting binary log, then MySQL server restarted. <br />
3. Application updated non-heap tables, some heap tables were deleted automatically. <br />
<br />
According to 5.6 reference manual, Sec 15.3 &quot;MEMORY Tables and Replication... DELETE statement is written to the master&#039;s binary log, to empty the table on the slaves also.&quot; <br />
<br />
My database is not replicate configuration, using just standalone.<br />
<br />
Your suggestion would be appreciated.<br />
Thanks<br />
<br />
kats]]></description>
            <dc:creator>Kats Sato</dc:creator>
            <category>Memory Storage Engine</category>
            <pubDate>Mon, 24 Nov 2014 04:17:43 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?92,615685,615685#msg-615685</guid>
            <title>Mysql Hangs (1 reply)</title>
            <link>https://forums.mysql.com/read.php?92,615685,615685#msg-615685</link>
            <description><![CDATA[ Dear Sir,<br />
<br />
    We are using an mysql 5.1,we are facing a problem of hang database.<br />
<br />
Regards,]]></description>
            <dc:creator>bilpy Thomas</dc:creator>
            <category>Memory Storage Engine</category>
            <pubDate>Fri, 27 Jun 2014 02:14:01 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?92,615532,615532#msg-615532</guid>
            <title>mysqlcheck information_schema (1 reply)</title>
            <link>https://forums.mysql.com/read.php?92,615532,615532#msg-615532</link>
            <description><![CDATA[ Hi, i have a problem. I have two same databases but i have a problem with the command : mysqlcheck --database.<br />
<br />
On the first, the command doesn&#039;t check information_schema and on the second, the commande check information_schema. I have the message :<br />
information_schema.TABLE_PRIVILEGES<br />
note     : The storage engine for the table doesn&#039;t support check<br />
<br />
I want that my check doesn&#039;t do on the second . Why does it do? <br />
Have you an idea?<br />
<br />
The version of mysql is  5.0.18<br />
<br />
Thanks]]></description>
            <dc:creator>sylvie de magalhaes</dc:creator>
            <category>Memory Storage Engine</category>
            <pubDate>Thu, 03 Jul 2014 01:41:40 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?92,612204,612204#msg-612204</guid>
            <title>Row size / column size on MEMORY engine (1 reply)</title>
            <link>https://forums.mysql.com/read.php?92,612204,612204#msg-612204</link>
            <description><![CDATA[ Hi,<br />
<br />
I am trying to create a my MEMORY table to cache frequently used data retrieved from a separate system via webservice. The following is the SQL statement:<br />
<br />
CREATE TABLE VplsL2AccessInterface (<br />
    objectFullName char(128) not null,<br />
    displayedName char(80),<br />
    description char(80),<br />
    actualMtu long,<br />
    administrativeState char(16),<br />
    egressFilterId long,<br />
    egressFilterName char(80),<br />
    egressFilterPointer char(128),<br />
    egressIpFilterId long,<br />
    egressMacFilterId long,<br />
    egressPolicyId long,<br />
    egressPolicyName char(80),<br />
    egressPolicyObjectPointer char(128),<br />
    encapType char(10),<br />
    ingressFilterId long,<br />
    ingressFilterName char(80),<br />
    ingressFilterPointer char(128),<br />
    ingressIpFilterId long,<br />
    ingressMacFilterId long,<br />
    ingressPolicyId long,<br />
    ingressPolicyName char(80),<br />
    innerEncapValue int,<br />
    nodeId char(16),<br />
    nodeName char(80),<br />
    operationalState char(16),<br />
    ossMetaData char(80),<br />
    outerEncapValue int,<br />
    portId long,<br />
    portIdentifyingName char(80),<br />
    portName char(80),<br />
    provisionedMtu long,<br />
    serviceId long,<br />
    serviceName char(80),<br />
    shcvSourceIpAddress char(16),<br />
    shgName char(80),<br />
    shgSitePointer char(128),<br />
    subscriberId long,<br />
    subscriberName char(80),<br />
    svcComponentId long,<br />
    terminatedObjectName char(80),<br />
    terminatedObjectPointer char(128)<br />
) ENGINE=Memory DEFAULT CHARSET=utf8;<br />
<br />
The char column type should be varchar, because the row in MEMORY table has to be fixed size. <br />
<br />
This statement gives me the following error:<br />
    Error Code: 1163. The used table type doesn&#039;t support BLOB/TEXT columns<br />
<br />
Apparently there&#039;s no BLOB or TEXT column in the table definition. Not sure if it&#039;s because of the row size, column size or number of columns in the table. But what are these limitations?<br />
<br />
Harry]]></description>
            <dc:creator>harry sheng</dc:creator>
            <category>Memory Storage Engine</category>
            <pubDate>Thu, 10 Apr 2014 14:52:50 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?92,612032,612032#msg-612032</guid>
            <title>Building Memory Table from AES Encrypted Physical Table (2 replies)</title>
            <link>https://forums.mysql.com/read.php?92,612032,612032#msg-612032</link>
            <description><![CDATA[ Dear All,<br />
<br />
I want to only store encrypted data on my website.  I have a tiny 3 column table (ID, Name, Address) for a test.  It is AES encrypted.  My thought is to create a memory table which will be non-encrypted and build it from the encrypted table on my application init.  So I was considering how to do this especially since the encrypted table structure is (ID-bigint autoincrement, Name-varbinary 200, Address-varbinary 200) and I want the resulting memory table to be (ID, bigint, Name varchar 100, Address varchar 100).  I don&#039;t want any physical intermediary unencrypted data. Here were statements inserting and retrieving the encrypted data:<br />
<br />
INSERT into user (first_name, address) VALUES (AES_ENCRYPT(&#039;Obama&#039;, &#039;usa2010&#039;),AES_ENCRYPT(&#039;Obama&#039;, &#039;usa2010&#039;));<br />
<br />
SELECT ID, AES_DECRYPT(first_name, &#039;usa2010&#039;), AES_DECRYPT(address, &#039;usa2010&#039;) from user;<br />
<br />
<br />
Any thoughts much appreciated including alternative approaches to just storing encrypted data.<br />
<br />
Thanks greatly,<br />
<br />
Lyle]]></description>
            <dc:creator>Lyle Holcomb</dc:creator>
            <category>Memory Storage Engine</category>
            <pubDate>Sat, 12 Apr 2014 05:17:34 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?92,587566,587566#msg-587566</guid>
            <title>Debugging Memory Engine Problem (3 replies)</title>
            <link>https://forums.mysql.com/read.php?92,587566,587566#msg-587566</link>
            <description><![CDATA[ I am getting a table full error when attempting to create a btree index for a Memory engine table. The table is able to load and I&#039;m able to generate a Hash index.<br />
I have 1 billion points in the table. I&#039;m able to store 100M points in the indexed table, but not much more than that. I&#039;ve tried setting the tmp_table_size and max_heap_table_size both in the client and in the my.cnf file with no luck.<br />
Any thoughts? <br />
Below are the particulars of the table and system<br />
<br />
-- I create a table:<br />
CREATE TABLE points_mem (val int, x int, y int) ENGINE = MEMORY  MAX_ROWS=5000000000;<br />
-- Then insert the points<br />
mysql&gt; INSERT INTO points_mem SELECT * FROM points;<br />
Query OK, 999950884 rows affected (17 min 20.99 sec)<br />
Records: 999950884  Duplicates: 0  Warnings: 0<br />
-- Fails when creating the Btree index<br />
<br />
mysql&gt; CREATE INDEX xy_index ON points_mem (x,y) USING BTREE;<br />
ERROR 1114 (HY000): The table &#039;#sql-f7f_23&#039; is full<br />
<br />
 <br />
-- I have set the system variables in the my.cnf file<br />
<br />
tmp_table_size=150G<br />
max_heap_table_size=150G<br />
<br />
-- The system is Linux Ubuntu 11.10 and the MySQL is 5.1<br />
<br />
-- It seems that there is memory, looking at output of &quot;free -g&quot; cmd<br />
<br />
free -g<br />
                     total       used            free     shared    buffers     cached<br />
Mem:           240             14           225          0          0               12<br />
-/+ buffers/cache:          2        238<br />
Swap:            0          0          0<br />
<br />
<br />
Thanks for the help]]></description>
            <dc:creator>Charles Earl</dc:creator>
            <category>Memory Storage Engine</category>
            <pubDate>Sat, 01 Jun 2013 01:55:52 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?92,584720,584720#msg-584720</guid>
            <title>In-memory dB on Embedded system. (1 reply)</title>
            <link>https://forums.mysql.com/read.php?92,584720,584720#msg-584720</link>
            <description><![CDATA[ Hi,<br />
<br />
I am a newbie in database. Please excuse me If my query sounds elementary.<br />
<br />
I have an Embedded Debian linux 2.6.35.9, mysql 5.1.<br />
<br />
My objective is to run the db in-memory, as in the long run it would damage the flash drive with too many read/write operations.<br />
<br />
Hence I want to run the db in-memory and to have data consistency, I want to write back the data to<br />
1. flash drive say every 2hrs(or may be less).<br />
2. Also during every system restart/shutdown, copy the data to/from memory from/to flash drive.<br />
<br />
Please help me with some pointers. I believe there exists some solution, as I have time constraints, I could not do exhaustive research. Hence any help is much appreciated.<br />
<br />
<br />
Thanks<br />
Sandhya]]></description>
            <dc:creator>Sandhya Srinivas</dc:creator>
            <category>Memory Storage Engine</category>
            <pubDate>Thu, 25 Apr 2013 15:10:22 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?92,580505,580505#msg-580505</guid>
            <title>No Limits - Memory Engine (10 replies)</title>
            <link>https://forums.mysql.com/read.php?92,580505,580505#msg-580505</link>
            <description><![CDATA[ Hello,<br />
<br />
I have a setup that kind of mimic in-memory database. I have a table created as memory engine and the same server is configured to act as master and slave. The slave is another database which has the same table structure, but the engine is innodb. Now, we all know that the maximum limits of memory engine and that is restricted to max_heap_table_size. Now that, we have this limitation,I had to ahve some kind of work around. My application was a logger that continuously wrote to this table (no updates/deletes) and then the reporting module read it off the slave for graphs and analytical information.<br />
So I decided to partition the memory engine based table on the master by primary key (hash partition) and there after even after 4M records, i dont see table full! <br />
<br />
here is how it is done:-<br />
<br />
CREATE TABLE `callstack` (<br />
  `instance_id` bigint(20) NOT NULL AUTO_INCREMENT,<br />
  `t_thread_id` varchar(64) DEFAULT NULL,<br />
  `s_id` varchar(64) DEFAULT NULL,<br />
  `t_host` varchar(30) DEFAULT NULL,<br />
  `s_t_id` varchar(64) DEFAULT NULL,<br />
  `p_s_t_id` varchar(64) DEFAULT NULL,<br />
  `service` varchar(30) DEFAULT NULL,<br />
  `ipa` varchar(50) DEFAULT NULL,<br />
  `c_time` bigint(20) DEFAULT NULL,<br />
  `duration` smallint(6) DEFAULT NULL,<br />
  `s_host` varchar(30) DEFAULT NULL,<br />
  `event` varchar(15) DEFAULT NULL,<br />
  `mode` varchar(10) DEFAULT NULL,<br />
  PRIMARY KEY (`instance_id`)<br />
) ENGINE=MEMORY DEFAULT CHARSET=latin1<br />
/*!50100 PARTITION BY HASH (instance_id)<br />
PARTITIONS 100 */<br />
<br />
Current Table status:=<br />
=====================<br />
<br />
mysql&gt;  show table status like &#039;callstack%&#039;;<br />
+-----------+--------+---------+------------+---------+----------------+-------------+-----------------+--------------+-----------+----------------+---------------------+-------------+------------+-------------------+----------+----------------+---------+<br />
| Name      | Engine | Version | Row_format | Rows    | Avg_row_length | Data_length | Max_data_length | Index_length | Data_free | Auto_increment | Create_time         | Update_time | Check_time | Collation         | Checksum | Create_options | Comment |<br />
+-----------+--------+---------+------------+---------+----------------+-------------+-----------------+--------------+-----------+----------------+---------------------+-------------+------------+-------------------+----------+----------------+---------+<br />
| callstack | MEMORY |      10 | Fixed      | 4370554 |            479 |  2095729600 |               0 |     90993600 |         0 |        4370555 | 2013-02-28 10:20:41 | NULL        | NULL       | latin1_swedish_ci |     NULL | partitioned    |         |<br />
+-----------+--------+---------+------------+---------+----------------+-------------+-----------------+--------------+-----------+----------------+---------------------+-------------+------------+-------------------+----------+----------------+---------+<br />
1 row in set (0.00 sec)<br />
<br />
max_heap_table_size variable<br />
============================<br />
<br />
mysql&gt; show variables like &#039;%heap%&#039;;<br />
+---------------------+-----------+<br />
| Variable_name       | Value     |<br />
+---------------------+-----------+<br />
| max_heap_table_size | 268435456 |<br />
+---------------------+-----------+<br />
1 row in set (0.00 sec)<br />
<br />
<br />
Is the memory engine broken or is this a edge case issue? But nonetheless, it is working for me as I wanted!<br />
<br />
Regards,<br />
Raghu]]></description>
            <dc:creator>Raghunandan Sastry</dc:creator>
            <category>Memory Storage Engine</category>
            <pubDate>Thu, 21 Mar 2013 01:19:08 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?92,577362,577362#msg-577362</guid>
            <title>Index for group by not working (no replies)</title>
            <link>https://forums.mysql.com/read.php?92,577362,577362#msg-577362</link>
            <description><![CDATA[ Adding indexes for group by optimization doesn&#039;t seem to work for heap tables. In the example below I create two tables - a standard MyISAM and a MEMORY one. The MyISAM table can group by far faster than the heap table, even though they&#039;re identical and both have BTREE index. Is it intentional that heap tables shouldn&#039;t use indexes for group by?<br />
<br />
<hr class="bbcode" />
<pre class="bbcode">-- Setting everything up

SET max_heap_table_size = 104857600;

CREATE TABLE lookup_mem
    (id INT, INDEX USING BTREE (id))
    ENGINE = MEMORY;

CREATE TABLE lookup_hdd
    (id INT, INDEX USING BTREE (id))
    ENGINE = MYISAM;


DELIMITER $$

CREATE PROCEDURE `populate_table`()
BEGIN
    DECLARE count INT DEFAULT 0;
    WHILE count &lt; 3000000 DO
        INSERT INTO lookup_mem SET id = ROUND(RAND()*100);
        SET count = count + 1;
    END WHILE;
END$$

DELIMITER ;



CALL populate_table;

INSERT INTO lookup_hdd SELECT * FROM lookup_mem;</pre>
<br />
<hr class="bbcode" />
<br />
Now to the fun stuff:<br />
<br />
<br />
<hr class="bbcode" />
<br />
<pre class="bbcode">EXPLAIN SELECT * FROM lookup_mem GROUP BY id;

-- gives
-- 1, SIMPLE, lookup_mem, index, , id, 5, , 3000000, 

EXPLAIN SELECT * FROM lookup_hdd GROUP BY id;

-- gives
-- 1, SIMPLE, lookup_hdd, range, , id, 5, , 101, Using index for group-by





SELECT * FROM lookup_mem GROUP BY id;

-- takes 1.216 seconds

SELECT * FROM lookup_hdd GROUP BY id;

-- takes 0.001 seconds</pre>
<br />
<hr class="bbcode" />
<br />
<br />
I&#039;m using mysql 5.5.29. I&#039;ve also tried this on 5.1 with the same results.]]></description>
            <dc:creator>Andy Svensson</dc:creator>
            <category>Memory Storage Engine</category>
            <pubDate>Tue, 15 Jan 2013 08:20:57 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?92,574874,574874#msg-574874</guid>
            <title>Use more CPU and Ram (1 reply)</title>
            <link>https://forums.mysql.com/read.php?92,574874,574874#msg-574874</link>
            <description><![CDATA[ Hi,<br />
<br />
Fist of all i&#039;d like to know if I am using 32bit mysql or 64bit when the result to SHOW GLOBAL VARIABLES LIKE &#039;version_compile_machine&#039;; query is x86. NOT x86_64! show variables like &#039;version_compile_machine&#039;; gives the same result.<br />
<br />
Secondly I&#039;d like to improve the performance of mysql when adding and retrieving data, I&#039;ve notice that only 30% cpu and 1-2% Ram are used. I am using InnoDb default storage engine (if that helps).<br />
<br />
Thank you.]]></description>
            <dc:creator>PF SQL</dc:creator>
            <category>Memory Storage Engine</category>
            <pubDate>Mon, 03 Dec 2012 01:46:54 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?92,573430,573430#msg-573430</guid>
            <title>Error 126 Incorrect key file for table (1 reply)</title>
            <link>https://forums.mysql.com/read.php?92,573430,573430#msg-573430</link>
            <description><![CDATA[ Hi ,<br />
<br />
I am getting error 126 while trying to join 2 tables.<br />
Is there any way to update tempdir path.<br />
I have this issue in Windows7 OS ans mysql5.5. I found one solution on net that using --tmpdir will change the tmp file path but when i tried mysql is not recognizing this option. <br />
<br />
Any help?]]></description>
            <dc:creator>sasmita sahoo</dc:creator>
            <category>Memory Storage Engine</category>
            <pubDate>Sun, 11 Nov 2012 16:42:44 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?92,573215,573215#msg-573215</guid>
            <title>Apparently enough max_heap_table_size but &quot;table is full&quot; (3 replies)</title>
            <link>https://forums.mysql.com/read.php?92,573215,573215#msg-573215</link>
            <description><![CDATA[ I am trying to load 2x10e9 data into a table created by memory storage engine.<br />
But mysql server claims &quot;table is full error&quot;. It will be great if some body could comment on how to avoid this.<br />
<br />
Estimated memory required to store the data and the index is around 500GB, <br />
according to the manual: <br />
<a href="https://dev.mysql.com/doc/refman/5.5/en/memory-storage-engine.html"  rel="nofollow">https://dev.mysql.com/doc/refman/5.5/en/memory-storage-engine.html</a><br />
<br />
&gt; SUM_OVER_ALL_BTREE_KEYS(max_length_of_key + sizeof(char*) * 4)<br />
&gt; + SUM_OVER_ALL_HASH_KEYS(sizeof(char*) * 2)<br />
&gt; + ALIGN(length_of_row+1, sizeof(char*))<br />
<br />
So, I allocated around 1.5TB memory to the max_heap_table_size so that the <br />
mysql is allowed to use the required memory size. <br />
<br />
But the &quot;table is full error&quot; persists. <br />
<br />
If I remove the ddl for creating index, the data load it self finished without <br />
any error. But after the data loading when I try to make btree index, the <br />
error &quot;table is full&quot; happens again. <br />
<br />
Hash index seems to be all right to create. Could somebody give me some advise <br />
on what I should do to create btree index on memory engine table with 2x10e9 size? <br />
<br />
This is the ddl for the table. <br />
<br />
##############################################<br />
<br />
create table table_a (<br />
  col1 int,<br />
  col2 int,<br />
  col3 float,<br />
  col4 float,<br />
  col5 varchar16<br />
) ENGINE = Memory;<br />
<br />
create index idx1 on table_a ( col1 ) using btree;<br />
create index idx2 on table_a ( col2 ) using btree;<br />
<br />
<br />
##############################################<br />
<br />
my.cnf<br />
<br />
##############################################<br />
<br />
max_heap_table_size = 1024*1024*1024*500*3<br />
<br />
##############################################<br />
<br />
<br />
System:<br />
<br />
Red hat linux 6.2, 64bit<br />
MySQL 5.5.21<br />
Physical memory 2.0TB]]></description>
            <dc:creator>研 柿原</dc:creator>
            <category>Memory Storage Engine</category>
            <pubDate>Sun, 18 Nov 2012 04:37:04 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?92,568079,568079#msg-568079</guid>
            <title>the table is full error using Memory Engine (4 replies)</title>
            <link>https://forums.mysql.com/read.php?92,568079,568079#msg-568079</link>
            <description><![CDATA[ Hello,<br />
<br />
I am creating and inserting records in a temporary table in a function that runs numerous times. My question is that if I continuously drop and then create table with new records which do not exceed max_table_heap_size, does it free MySQL heap?<br />
<br />
I am facing &quot;the table is full&quot; error but maximum no. of records inserted do not exceed 10000.]]></description>
            <dc:creator>Adnan Raza</dc:creator>
            <category>Memory Storage Engine</category>
            <pubDate>Thu, 13 Sep 2012 02:25:55 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?92,568073,568073#msg-568073</guid>
            <title>Table is full error problem (no replies)</title>
            <link>https://forums.mysql.com/read.php?92,568073,568073#msg-568073</link>
            <description><![CDATA[ Hello,<br />
<br />
I have created and inserted records in a temporary table which has its engine=MEMORY, now the problem is that whenever records go up to 37000, it gives out an error, table is full.<br />
<br />
the temp table has only three fields and not much data and the max_heap_table_size = 16777216 which is 16 MB.<br />
<br />
I really can&#039;t understand why is 16 MB becoming insufficient...]]></description>
            <dc:creator>Adnan Raza</dc:creator>
            <category>Memory Storage Engine</category>
            <pubDate>Mon, 10 Sep 2012 10:37:43 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?92,565771,565771#msg-565771</guid>
            <title>IMDB data processing (1 reply)</title>
            <link>https://forums.mysql.com/read.php?92,565771,565771#msg-565771</link>
            <description><![CDATA[ Hi all,<br />
<br />
<br />
I need a fast processing of a small amount of data (up to 300K lines in max.). <br />
I need to calculate durations between 2 entries in 2 different tables (1 is a filtered copy, which contains less data).<br />
<br />
the table structure is very simple:<br />
<br />
table a and table b looks like the following:<br />
{<br />
 key   varchar(50) &lt;-- which is a GUID<br />
 key2  varchar(50) &lt;-- which is a GUID<br />
 ts    datetime <br />
 event varchar(50)<br />
 duration int<br />
}<br />
<br />
<br />
table a contains 300K rows, table b contains values from table a where a special &quot;event&quot; is set (lets say only 200K rows).<br />
<br />
now I do the following to calculate the durations:<br />
<br />
for each line in table a lookup the next entry in table b where the key2 is the same but b.ts greater a.ts. with the result table a will be updated...<br />
<br />
To be honest nothing serious, on my win32 test-machine (shame on me) I installed mySQL and craeted the tables. For my test case I loaded the data from the file and created a small procedure to test the case.<br />
<br />
Fist of all: I aborted the test after 3 hours (MS SQL Server does it in 2) but I think it could be OS related since I think that windows stored the mysql process memory in the pagefile (that could be the cause why the hdd led was continously flashing)...<br />
<br />
Does anyone had realized the same ?<br />
Is it faster on linux os or are there configuration switches which can improve this ?<br />
<br />
If necessary I can provide the procedure and tables (and 40 MB compressed data), but for this case I think it is not necessary...<br />
<br />
Thanks for any idea / help !<br />
<br />
<br />
Kind regards<br />
<br />
Christian]]></description>
            <dc:creator>Christian Wallukat</dc:creator>
            <category>Memory Storage Engine</category>
            <pubDate>Fri, 24 Aug 2012 14:44:35 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?92,562636,562636#msg-562636</guid>
            <title>&quot;#1030 - Got error 28 from storage engine&quot; (1 reply)</title>
            <link>https://forums.mysql.com/read.php?92,562636,562636#msg-562636</link>
            <description><![CDATA[ I am getting this error when I try to see the SCTRUTURE of a table in my database:<br />
&quot;#1030 - Got error 28 from storage engine&quot;<br />
<br />
Also, the commands to clean and eliminate the table are not working. I tried to empty the TMP folder in server directory, but it did not work. Also tried to OPTIMIZE the table, in PHPMYADMIN, but also no results.<br />
<br />
thanks for any suggestions!]]></description>
            <dc:creator>Jorge Elias</dc:creator>
            <category>Memory Storage Engine</category>
            <pubDate>Fri, 27 Jul 2012 05:51:47 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?92,554136,554136#msg-554136</guid>
            <title>How to use memcached_functions_mysql at mysql layer (1 reply)</title>
            <link>https://forums.mysql.com/read.php?92,554136,554136#msg-554136</link>
            <description><![CDATA[ I have installed mysql server 5.5, memcached, libmemcache and<br />
memcached_functions_mysql.<br />
<br />
Now I want to use it on my slow queries like SELECT statement.<br />
<br />
Say I want to cache below query on mysql layer<br />
<br />
SELECT * FROM payements;<br />
<br />
How do i cache it on mysql layer.]]></description>
            <dc:creator>Supriya Mayekar</dc:creator>
            <category>Memory Storage Engine</category>
            <pubDate>Thu, 14 Jun 2012 04:24:18 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?92,519064,519064#msg-519064</guid>
            <title>table size growth (3 replies)</title>
            <link>https://forums.mysql.com/read.php?92,519064,519064#msg-519064</link>
            <description><![CDATA[ Hello all,<br />
<br />
I&#039;ve been monitoring the size of our memory tables for a few weeks now (with Cacti actually). And I noticed that the table size isn&#039;t growing linearly but from time to time.. for example, I had a 700 MB table which increased by 500 MB suddenly.<br />
<br />
I think it may be logical since the engine is memory and its allocation cost a lot of CPU.. so MySQL probably allocates memory space by segment.<br />
<br />
So, I&#039;d like to know two things. First, is my theory correct? and then, how can I tune this behavior?<br />
<br />
<br />
Thank you for your help.<br />
<br />
Ben]]></description>
            <dc:creator>Benjamin Tuffreau</dc:creator>
            <category>Memory Storage Engine</category>
            <pubDate>Sat, 10 Mar 2012 17:47:08 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?92,510484,510484#msg-510484</guid>
            <title>Mysql Memory table getting many locks (1 reply)</title>
            <link>https://forums.mysql.com/read.php?92,510484,510484#msg-510484</link>
            <description><![CDATA[ On my site I log every pageview (date, ip, referrer, page, etc) in a simple mysql table.<br />
<br />
This table gets 1 SELECT queriy per minute, 1 delete query per minute, no UPDATE queries, but a LOT of INSERTS. (about 300 per second).<br />
<br />
This table is never bigger than 200MB.<br />
<br />
Today I changed this table from an InnoDB table to a MEMORY table, this made sense to me to prevent unnecessary hard disk IO. I also prune this table once per minute, to make sure it never get&#039;s too big. And this information is not very important, so on restart of MySQL it does not matter that it is removed.<br />
<br />
--<br />
<br />
Performance wise, things are running fine. But I noticed that while running tuning-primer, that my **Current Lock Wait ratio** is quite high using MEMORY table.<br />
<br />
    Current Lock Wait ratio = 1 : 561<br />
<br />
If I change this table to InnoDB the ratio is:<br />
<br />
    Current Lock Wait ratio = 0 : 78600946<br />
<br />
My question: Should I worry about this Lock Wait Ratio? And is there something I can change in my configuration to improve things so that the lock wait ratio isn&#039;t so high using MEMORY tables?]]></description>
            <dc:creator>boon m</dc:creator>
            <category>Memory Storage Engine</category>
            <pubDate>Sun, 22 Jan 2012 01:48:26 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?92,490510,490510#msg-490510</guid>
            <title>Memory load extremely high (1 reply)</title>
            <link>https://forums.mysql.com/read.php?92,490510,490510#msg-490510</link>
            <description><![CDATA[ Hello,<br />
<br />
When I request SELECT * FROM dev_dwh.ods_ventes o on the table that contains 85 billion of rows, following message ‘The memory load of the system is extremely high. This is likely because of the current result being very large’  displays in about 1,5 billion of extracted rows.<br />
<br />
How to do to extract the 85 millions of rows? Is it possible? Should it parameter anything in MYSQL Server? Or perhaps in RAM memory windows server?<br />
<br />
Thank you very much for your help.<br />
<br />
Best regards,<br />
<br />
Christopher]]></description>
            <dc:creator>bastide christopge</dc:creator>
            <category>Memory Storage Engine</category>
            <pubDate>Sun, 30 Oct 2011 21:54:07 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?92,430437,430437#msg-430437</guid>
            <title>Memory + MAX_ROWS (hash rebuild) quick question (no replies)</title>
            <link>https://forums.mysql.com/read.php?92,430437,430437#msg-430437</link>
            <description><![CDATA[ For reference, from <a href="http://dev.mysql.com/doc/refman/5.5/en/memory-storage-engine.html"  rel="nofollow">http://dev.mysql.com/doc/refman/5.5/en/memory-storage-engine.html</a>:<br />
<pre class="bbcode">
You can also specify a MAX_ROWS table option in CREATE TABLE statements for
MEMORY tables to provide a hint about the number of rows you plan to store in
 them. This does not enable the table to grow beyond the max_heap_table_size
 value, which still acts as a constraint on maximum table size. For maximum 
flexibility in being able to use MAX_ROWS, set max_heap_table_size at least as
 high as the value to which you want each MEMORY table to be able to grow.</pre>
<br />
I know Hashing (and Hash Indexes for the Memory engine) are complicated subjects, but if nothing else, hopefully the answer to this question will help me understand better:<br />
<br />
My current understanding (even as a software engineer) is that for most Hash implementations, (such as a Java HashMap), you must specify an upper-bound for the hash (to avoid the hash from having to be recalculated [rebuilt] every so often for inserts, to maintain O(1) lookup performance). Is that the purpose of MAX_ROWS in the Memory engine?<br />
<br />
Thanks,<br />
- John]]></description>
            <dc:creator>John Nahlen</dc:creator>
            <category>Memory Storage Engine</category>
            <pubDate>Fri, 12 Aug 2011 05:29:34 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?92,427111,427111#msg-427111</guid>
            <title>Unable to delete records or truncate temporary memory tables (no replies)</title>
            <link>https://forums.mysql.com/read.php?92,427111,427111#msg-427111</link>
            <description><![CDATA[ hi<br />
i am trying to delete datas from a temporary table, but its failing.<br />
<br />
Please help me]]></description>
            <dc:creator>Meenakshi SUndara Santhosh</dc:creator>
            <category>Memory Storage Engine</category>
            <pubDate>Sat, 16 Jul 2011 10:49:57 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?92,426686,426686#msg-426686</guid>
            <title>memory engine opimization (no replies)</title>
            <link>https://forums.mysql.com/read.php?92,426686,426686#msg-426686</link>
            <description><![CDATA[ sir<br />
<br />
i have 64 bit windows7 os with 64bit 5.1.48 version mysql.<br />
i have 72 lakes recored in the memory table with 280.8mb data length<br />
when i run the query it take 2 min to show the result. but i want it within 1 sec.<br />
<br />
if i have to change any thing in my.ini file ,than what details should i change <br />
so that it comes within 1 sec.<br />
<br />
<br />
can any one help me<br />
regards <br />
deva]]></description>
            <dc:creator>deva clementraj</dc:creator>
            <category>Memory Storage Engine</category>
            <pubDate>Wed, 13 Jul 2011 12:40:59 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?92,425906,425906#msg-425906</guid>
            <title>best practices for variable size limitation (no replies)</title>
            <link>https://forums.mysql.com/read.php?92,425906,425906#msg-425906</link>
            <description><![CDATA[ hi guys,<br />
<br />
from the limitation presented for myslq RAM tables, what is best practice for storing large pieces of text or binary data?<br />
<br />
i found this project: <a href="http://code.google.com/p/mysql-heap-dynamic-rows/"  rel="nofollow">http://code.google.com/p/mysql-heap-dynamic-rows/</a><br />
but i&#039;m not sure i want to maintain someone else&#039;s code for production...<br />
<br />
since a mem table has a default size of 16M, maybe it makes sense to strip text across multiple rows?<br />
<br />
how will or did you approach this limitation?<br />
<br />
thanks for your help.<br />
<br />
~nir.]]></description>
            <dc:creator>NOT_FOUND NOT_FOUND</dc:creator>
            <category>Memory Storage Engine</category>
            <pubDate>Wed, 06 Jul 2011 20:40:37 +0000</pubDate>
        </item>
    </channel>
</rss>
