Re: Found a possible replication bug in 5.5.8/5.5.11 (auto-increment in primary key)

2011-06-14 Thread Claudio Nanni
Very interesting. Waiting for update. On Jun 15, 2011 4:51 AM, "Hank" wrote: > > The slave is receiving "null" as the statement based insert, not an out of > range number from the master. > > I've been doing more research all day on this bug and have a bit more > information as to what's causing i

Re: Found a possible replication bug in 5.5.8/5.5.11 (auto-increment in primary key)

2011-06-14 Thread Hank
The slave is receiving "null" as the statement based insert, not an out of range number from the master. I've been doing more research all day on this bug and have a bit more information as to what's causing it. I plan to write it up tomorrow and post it. Basically, everything works perfectly, u

Re: Found a possible replication bug in 5.5.8/5.5.11 (auto-increment in primary key)

2011-06-14 Thread Hal�sz S�ndor
2011/06/13 22:38 -0400, Hank But that bug report was closed two years ago. I have no idea if it's the server sending bad data or the slaves. I think it's the slaves, because on the slave error, it clearly is getting this statement: "insert into test values (1,null)" to replicate, but wh

Re: Data missing after field optimization

2011-06-14 Thread Johan De Meersman
Heeh. That's not a random blog post, that's the official manual :-p If it's in there, it's pretty much trustworthy; and I've learned something new :-) So apparently there's a dedicated "NULL" bit to columns... Yes, then there would be a small performance benefit. I stand corrected. Still, as yo

Re: optimization strategies based on file-level storage

2011-06-14 Thread Johan De Meersman
- Original Message - > From: "Bennett Haselton" > > modifications. (For example, the question I asked earlier about > whether you can declare extra space at the end of each row that is > "reserved for future columns".) That question I can answer: you can't "reserve" space, but if you

Re: Data missing after field optimization

2011-06-14 Thread sono-io
On Jun 7, 2011, at 10:43 PM, Johan De Meersman wrote: > Where did you find the advice about setting columns NOT NULL? It took me awhile, but I just found it again, in case anyone is interested: http://dev.mysql.com/doc/refman/5.0/en/data-size.html 7.8.1. Make Your Data as Small as Pos

Re: Found a possible replication bug in 5.5.8/5.5.11 (auto-increment in primary key)

2011-06-14 Thread Hank
That is the slave relay log dump I posted (and mis-labeled). Thanks. -Hank On Tue, Jun 14, 2011 at 2:34 AM, Claudio Nanni wrote: > You should also have a look at the slave relay log. > > But in any case sounds like a bug. > > Claudio > On Jun 14, 2011 5:18 AM, "Hank" wrote: > > Both my master a

RE: optimization strategies based on file-level storage

2011-06-14 Thread Bennett Haselton
At 05:46 AM 6/14/2011, Carlos Eduardo Caldi wrote: Hello Bennett On the Mysql developer site have a grate documentation, try the links above. http://dev.mysql.com/doc/refman/5.0/en/optimizing-database-structure.html http://dev.mysql.com/doc/refman/5.0/en/data-size.html Thanks, this gets me

optimization strategies based on file-level storage

2011-06-14 Thread Bennett Haselton
I'm looking for some tips & tricks documentation that explains how different data types in rows are stored at the file level (in MyISAM tables, at least), and how to optimize tables for faster queries, updates, table definition modification, etc. based on this knowledge. For example, I've hear