MySQL Bugs: #1740: Blob-Space required

Bug #1740	Blob-Space required
Submitted:	3 Nov 2003 3:03	Modified:	23 Jan 2006 16:06
Reporter:	Thomas Mayer	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: MyISAM storage engine	Severity:	S4 (Feature request)
Version:	all	OS:	Any (all)
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
Hi,

I have some trouble using a table containing data combined with blob-Fields.

The table is getting very huge (> 2,000,000 records) and contains data and a blob field with a JPG in every record.

Performance is getting very slow, but I use indeces and do some FORCE INDEX which works as EXPLAIN explains.

Most Queries on the table are slow.

So I use a second table containing only the data and another containing the blob-fields. Then I do Querys on the blob-free table with force index and join the blob data.

This works not that bad but I now have redundancy in my ERM.

How to repeat:
Create a very big table with blobs and fill it with content.
Do some queries on the table and see what performance you have with or without blobs.

Suggested fix:
What about creating something like a Blob Space which separates blob data automatically when using blob fields? Informix f.e. does that, I believe.

The blob data could be within a separate file like we have it with table-data and indeces on MyIsam. Maybe this was also something for InnoDb.

So it mainly would be something for the different table-handlers.

If you split your table leaving the blob files on another one and having an identifier
column type int not resolve your issue?.

Thanks in advance.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".