English
| Previous 30 Newer Entries | Showing entries 61 to 74 |
How would you expect AUTO_INCREMENT to work with MERGE tables ? Assuming INSERT_METHOD=LAST is used I would expect it to work same as in case insertion happens to the last table... which does not seems to be the case. Alternatively I would expect AUTO_INCREMENT to be based off the maximum value across all tables, respecting AUTO_INCREMENT set for the Merge Table itself. Neither of these expectations really true:
PLAIN TEXT SQL:Over a year ago I wrote about pretty nasty Innodb Recovery Bug. I ran in the same situation again (different system, different customer) and went to see the status of the bug... and it is still open.
You may thing it is minor issue but in fact with large buffer pool this bug makes database virtually unrecoverable (if 10% of progress in 2hours qualifies as that). It is especially nasty as it is quite hard to predict. Both customers had MySQL crash recovery happening in reasonable time... most of the times until they run into this problem.
So what is the point ? Have modest expectations about when your favorite MySQL bugs are fixed (This is actually Innodb one, so
[Read more...]I don’t know about “me too” types of bug replies, but before everyone goes to the bug database and starts saying “me too”, “this affects me”, “please fix this ASAP”, “I won’t use MySQL 5.1 till this is fixed”, I wonder if this will cause more harm (i.e. more bug spam for the developer, and all those subscribed to it) than good.
It seems like the public Worklog interface gets this right - via voting. Having a count of those that have the same problems, even displayed via “stars”, is
-0
This is a short reply to Michael’s post “A bugs life”.
This bugs are still relevant for me:
In my dreamland they would be fixed before 5.1 reaches GA but I know that probably it is difficult to add such features in a RC version.
Questions. Do you plan to fix them? If yes, can I ask you when?
Thanks.
According to the manual, FLUSH LOGS is supposed to:
Closes and reopens all log files. If binary logging is enabled, the sequence number of the binary log file is incremented by one relative to the previous file. On Unix, this is the same thing as sending a SIGHUP signal to the mysqld server (except on some Mac OS X 10.3 versions where mysqld ignores SIGHUP and SIGQUIT).
If the server is writing error output to a named file (for example, if it was started with the –log-error option), FLUSH LOGS causes it to rename the current error log file with a suffix of -old and create a new empty log file. No renaming occurs if the server is not writing to a named file (for example, if it is writing errors to the console).
There is a bug, however. In the case when the error log
[Read more...]We’ve always had some pending/unresolved issues, and I think that as our tracking gets better, there’s likely to be more of them. A number of bug-reports are either hard to reproduce (often including from the reporter) or end up without updates etc.
Zack Urlocker says MySQL 5.1 has zero bugs. He may have been misquoted, or quoted out of context, but there it is. I’ll quote enough of it that you can’t take it out of context twice:
[Read more...]Mickos also said MySQL 5.1 has upgraded its reliability and ease of use over 2005’s v5.0.
“Now we can admit it, but this version is much improved over 5.0, which we weren’t totally happy with,” Mickos confided.
He reported that more than 1,300 bugs (997 in 2007, 386 so far in 2008) have been fixed in v5.1, and that, according to standard DBT2 benchmarks, the performance of v5.1 is 10 to 15 percent better than the previous version.
“This version now has zero bugs,” Urlocker told eWEEK.
ODBC_BOTH_DSN, which means you have to keep resetting it to the correct value after nearly every installer api call. this problem is platform-agnostic — the iodbc code is just plain wrong.
-0
MySQL is listing a good overview of the bugs they still have open in 5.1
This list comes very handy as I have on my todolist to figure out which bugs they still have open in 5.1 Cluster to see if we are impacted by one or more of them.
Now I don't have to manually go trough the lists anymore ..
thnx MySQL !
-0
Fortune Cookie at the MySQL Pre-Conference Party.
-0
-0
| Previous 30 Newer Entries | Showing entries 61 to 74 |