MySQL Forums
Forum List  »  Partitioning

MySQL 5.5.24 Server Crash
Posted by: Bryce Byrd
Date: July 13, 2012 08:48AM

Greetings! I have a table defined as follows. When we try to select from the table on a value where the partition doesn't exist, mysql crashes. The MySQL Version is 5.5.24 and we're running Windows Server 2003 64 bit. I found one bug that might be related to this but its for 5.5.25 and CentOS so not sure if I should tag this to it, or start another, or if there's something I just have jacked up in my create table.

CREATE TABLE `AssessorLand` (
`MM_FIPS_STATE_CODE` TINYINT(2) UNSIGNED NOT NULL DEFAULT '0',
`MM_FIPS_MUNI_CODE` SMALLINT(3) UNSIGNED NOT NULL DEFAULT '0',
`SA_PROPERTY_ID` INT(10) UNSIGNED NOT NULL DEFAULT '0',
`ACRES` VARCHAR(15) DEFAULT NULL,
`FRONTAGE` VARCHAR(7) DEFAULT NULL,
`DEPTH` VARCHAR(7) DEFAULT NULL,
`WATER` CHAR(2) DEFAULT NULL,
`SEWER` CHAR(2) DEFAULT NULL,
`GAS` CHAR(2) DEFAULT NULL,
`ELECTRIC` CHAR(2) DEFAULT NULL,
`ROAD_TYPE` CHAR(3) DEFAULT NULL,
`LEGAL_DESC` VARCHAR(104) DEFAULT NULL,
`SUBDIVISN` CHAR(5) DEFAULT NULL,
`TOTAL_VALU` VARCHAR(11) DEFAULT NULL,
`LAND_VALUE` VARCHAR(11) DEFAULT NULL,
`NEIGHBOR` VARCHAR(10) DEFAULT NULL,
`NEGHBR_TYP` CHAR(4) DEFAULT NULL,
`IRREGULAR` CHAR(1) DEFAULT NULL,
`TERRAIN` CHAR(3) DEFAULT NULL,
`RED_2HALF` VARCHAR(13) DEFAULT NULL,
`NET_TAX` VARCHAR(13) DEFAULT NULL,
`ZONING` VARCHAR(6) DEFAULT NULL,
`LastModifiedAt` TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
PRIMARY KEY (`MM_FIPS_STATE_CODE`,`MM_FIPS_MUNI_CODE`,`SA_PROPERTY_ID`),
KEY `idx__SA_PROPERTY_ID` (`SA_PROPERTY_ID`)
) ENGINE=INNODB DEFAULT CHARSET=latin1 ROW_FORMAT=COMPRESSED KEY_BLOCK_SIZE=8
PARTITION BY LIST (MM_FIPS_STATE_CODE)
(PARTITION AL VALUES IN (1) ENGINE = InnoDB,
PARTITION AK VALUES IN (2) ENGINE = InnoDB,
PARTITION AZ VALUES IN (4) ENGINE = InnoDB,
PARTITION AR VALUES IN (5) ENGINE = InnoDB,
PARTITION CA VALUES IN (6) ENGINE = InnoDB,
PARTITION CO VALUES IN (8) ENGINE = InnoDB,
PARTITION CT VALUES IN (9) ENGINE = InnoDB,
PARTITION DE VALUES IN (10) ENGINE = InnoDB,
PARTITION DC VALUES IN (11) ENGINE = InnoDB,
PARTITION FL VALUES IN (12) ENGINE = InnoDB,
PARTITION GA VALUES IN (13) ENGINE = InnoDB,
PARTITION HI VALUES IN (15) ENGINE = InnoDB,
PARTITION ID VALUES IN (16) ENGINE = InnoDB,
PARTITION IL VALUES IN (17) ENGINE = InnoDB,
PARTITION `IN` VALUES IN (18) ENGINE = InnoDB,
PARTITION IA VALUES IN (19) ENGINE = InnoDB,
PARTITION KS VALUES IN (20) ENGINE = InnoDB,
PARTITION KY VALUES IN (21) ENGINE = InnoDB,
PARTITION LA VALUES IN (22) ENGINE = InnoDB,
PARTITION ME VALUES IN (23) ENGINE = InnoDB,
PARTITION MD VALUES IN (24) ENGINE = InnoDB,
PARTITION MA VALUES IN (25) ENGINE = InnoDB,
PARTITION MI VALUES IN (26) ENGINE = InnoDB,
PARTITION MN VALUES IN (27) ENGINE = InnoDB,
PARTITION MS VALUES IN (28) ENGINE = InnoDB,
PARTITION MO VALUES IN (29) ENGINE = InnoDB,
PARTITION MT VALUES IN (30) ENGINE = InnoDB,
PARTITION NE VALUES IN (31) ENGINE = InnoDB,
PARTITION NV VALUES IN (32) ENGINE = InnoDB,
PARTITION NH VALUES IN (33) ENGINE = InnoDB,
PARTITION NJ VALUES IN (34) ENGINE = InnoDB,
PARTITION NM VALUES IN (35) ENGINE = InnoDB,
PARTITION NY VALUES IN (36) ENGINE = InnoDB,
PARTITION NC VALUES IN (37) ENGINE = InnoDB,
PARTITION ND VALUES IN (38) ENGINE = InnoDB,
PARTITION OH VALUES IN (39) ENGINE = InnoDB,
PARTITION OK VALUES IN (40) ENGINE = InnoDB,
PARTITION `OR` VALUES IN (41) ENGINE = InnoDB,
PARTITION PA VALUES IN (42) ENGINE = InnoDB,
PARTITION RI VALUES IN (44) ENGINE = InnoDB,
PARTITION SC VALUES IN (45) ENGINE = InnoDB,
PARTITION SD VALUES IN (46) ENGINE = InnoDB,
PARTITION TN VALUES IN (47) ENGINE = InnoDB,
PARTITION TX VALUES IN (48) ENGINE = InnoDB,
PARTITION UT VALUES IN (49) ENGINE = InnoDB,
PARTITION VT VALUES IN (50) ENGINE = InnoDB,
PARTITION VA VALUES IN (51) ENGINE = InnoDB,
PARTITION WA VALUES IN (53) ENGINE = InnoDB,
PARTITION WV VALUES IN (54) ENGINE = InnoDB,
PARTITION WI VALUES IN (55) ENGINE = InnoDB,
PARTITION WY VALUES IN (56) ENGINE = InnoDB)

So if you do "SELECTION * FROM AssessorLand WHERE MM_FIPS_STATE_CODE = 3" the server crashes, there is no partition 3.

If anyone has any advice, I'd appreciate it.

Thanks.

Options: ReplyQuote


Subject
Views
Written By
Posted
MySQL 5.5.24 Server Crash
2799
July 13, 2012 08:48AM
1179
July 17, 2012 02:30PM


Sorry, you can't reply to this topic. It has been closed.

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.