Re: MySQL crashes
Charlene wrote: Anybody have any idea why MySQL would start to have this error message every 4 or so days at midnight: Do look at the logs, but if the error always occurs at midnight, you might look for a disk backup or compression program that's scheduled to run than and accesses the database files incompatibly. Cheers, Ann -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: how things get messed up
Martijn Tonies wrote: For example, the Firebird DBMS stores (longer) Blob data not right there in the record, so whenever you don't request the blob (that is, not selecting it), it ignores it completely and it can go through the file quickly. As do most of the MySQL storage engines. InnoDB uses a variety of strategies, http://www.innodb.com/doc/innodb_plugin-1.0/innodb-row-format.html MyISAM uses a strategy more like Firebird http://dev.mysql.com/doc/refman/5.0/en/storage-requirements.html And here's a comment from a very experienced MySQL DBA http://sheeri.com/archives/39 > But they do seem to store "in line", right? If not, why would there be > any performance problems? There are lots of ways to screw up storage. Cheers, Ann -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: how things get messed up
Martijn Tonies wrote: For example, the Firebird DBMS stores (longer) Blob data not right there in the record, so whenever you don't request the blob (that is, not selecting it), it ignores it completely and it can go through the file quickly. As do most of the MySQL storage engines. Cheers, Ann -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: MySQL 6.0.2-alpha and Falcon and possible bug/problem
Mariella Petrini wrote: ...MySQL 6.0.2 with Falcon on Linux with Debian 4. I have compiled the source code for 64 bit executable. The system is an Intel 2 cpus 4 cores each, with 8 GB of RAM. After having created approximately 8,500 empty tables mysqld server was still alive, you could connect with the mysql client, but any command that you would type would freeze (never come back). It would be interesting to get a stack trace at that point. We do have tests that create that many tables, so the problem is going to take some thought. I will try to re-run the same job, enabling falcon_debug_mask and see if I can get more info and repeat the problem. Sounds good - that can produce a LOT of output... so be sure to redirect it to a file. Best regards, Ann -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL 6.0.2-alpha and Falcon and possible bug/problem
Mathieu Bruneau wrote: I never tried the falcon engine, but could it be that mysql is running out of file descriptor ? That's less likely with Falcon than with engines that put each table and index in its own file. By default, Falcon tables share a single tablespace. Regards, Ann -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Blob data
Rick James wrote: Instead I broke blobs into pieces, inserting them with a sequence number. Understanding the underlying problem, that still seems like an unnatural way to store pictures and documents. Added benefit: Does not clog up replication while huge single-insert is being copied over network and reexecuted on slaves. The design of blobs that Jim did at DEC included the ability to send them across the network in chunks of a client specified size. In 1982 it was quite common to have blobs that were larger than physical memory. What he did more recently was add a "blob repository" separate from the active tablespace that allowed the backup function to skip unchanged blobs while backing up active data. It also allows replicants to share a single copy of blobs, if appropriate. There are lots of ways of making large blobs work better in relational databases. Regards, Ann -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
