Just found this little handy feature today:

So now if you press CTRL-C MySQL Command Line Client will not exit but will terminate query being executed. This is great as so many queries assumed CTRL-C would also abort running query in previous MySQL versions and I've seen many monstrous queries left running without noticing just because people would think CTRL-C terminated the query. Now it finally really does.

Great Job! I wish I would see more of such relatively simple but very handy improvements

I filed the following bug today. Basically it looks like in certain conditions Innodb may be started twice in the parallel on the same data files which can hurt database badly. It is true it does not seems to be 100% repeatable but I've seen it multiple times in different environments. I'm not sure if this is some platform which has issues with locking, Some race condition which allows to copies to start or anything else.

In any case you'we been warned - be careful and ensure MySQL is not already started when you're thinking to start one. Now when
MySQL starts to listen to the socket after Innodb Recovery is completed it is very easy to make a mistake and think MySQL is not running at all when recovery is in progress.

dbanotes posted a photo:

今天下午,我将搭乘海南航空的航班,回到杭州,结束这次广州之行.

这次见到了很多很好的朋友,也见识了一直奋斗在广东的兄弟.有很多感触.

非常感谢sybase的周老大的招待,以前我们是客户,现在我们是朋友,下次有机会一定要来杭州,我们再去喝茶.

还有无言,中午上班的时候和周老大一起跨过珠江过来陪我吃饭,这感情多好,可惜的是上次去杭州的时候,我刚好在外面出差.只能说友情后补了.

还有老刘,每次来广州,都会找他蹭饭,嗯,找的那个饭店的饭,真的很不错,还居然因为出差和我说没有招待好.太客气了.去杭州,一定要找我,好好的招待招待你.

最为重要的是应该感谢tommy,给我一个接触如此巨大的系统的机会,让自己发现,原来自己还有很多东西不懂,技术上,交际上,还有很多需要提高的地方,无论如何,我相信我会努力的去作的更好,不让老板失望,不让公司失望.作最好的自己,让自己作的更好,下一个目标,希望能将我们那里作的和广东一样的好.我会尽力的.

 广东的兄弟们,也给我很多很大的帮助,他们精湛的技术,细心的指导,还有中午食堂的饭.广州之行,快乐之旅.

 

It’s been a while since our last reader survey, and we’ve seen lots of change since the move to the new server in December. But some things haven’t changed a bit: We’re always looking for ways to improve Red Hat Magazine, and we love to have your input. So, if you would, please take a few minutes to answer these questions. Tell us your likes, dislikes, and ideas for the future. We’re listening.

       需要写一个简单的脚本，将所有数据文件、控制文件、在线日志文件等输出到一个文件中，一口气写完之后，发现输出结果中每行之间都有一空行，非常不爽，研究了一下 sqlplus 的设置参数之后解决了问题，把几个常用的参数在这里做一个小结，方便以后查询。

set echo on/off                     是否显示脚本中的需要执行的命令
set feedback on/off               是否显示 select 结果之后返回多少行的提示
set linesize n                          设置一行最多显示多少字符，之前就是因为 n 设得过大，导致行与行之间有空白行
set termout on/off                 在执行脚本时是否在屏幕上输出结果，如果 spool 到文件可以将其关闭
set heading on/off                 是否显示查询结果的列名，如果设置为 off，将用空白行代替，如果要去除该空白行，可以用 set pagesize 0
set pagesize n                        设置每页的行数，将 n 设为 0 可以不显示所有 headings, page breaks, titles, the initial blank line, and other formatting information
set  trimspool on/off               在 spool 到文件时是否去除输出结果中行末尾的空白字符，之前的隔行可以用该参数去掉，和该参数对应的是 trimout，后者用于屏幕输出
set trimout on/off                   是否去掉屏幕上输出结果行末尾的空白字符

The 49th edition of Log Buffer, the weekly review of database blogs, has been published by Coskan Gundogar on Coskans Approach to Oracle. The slot for the landmark 50th Log Buffer is still up for grabs. Get in touch to take it on and join the big conversation this is LB! Coskan Gundogar’s Log Buffer #49.