Comments on: Future InnoDB File Formats http://www.mysqlperformanceblog.com/2008/04/15/future-innodb-file-formats/ Everything about MySQL Performance Sat, 07 Nov 2009 18:35:44 -0800 http://wordpress.org/?v=2.8.4 hourly 1 By: porpoise http://www.mysqlperformanceblog.com/2008/04/15/future-innodb-file-formats/comment-page-1/#comment-284379 porpoise Mon, 21 Apr 2008 12:05:25 +0000 http://www.mysqlperformanceblog.com/2008/04/15/future-innodb-file-formats/#comment-284379 [...] Kangaroo, Leopard, Moose, Nautilus, Ocelot, Porpoise, Quail, Rabbit, Shark, Tiger, Urchin, Vipehttp://www.mysqlperformanceblog.com/2008/04/15/future-innodb-file-formats/Porpoise washed up near shipwreck prestontoday.netCrowds looked on after a porpoise was washed up [...] [...] Kangaroo, Leopard, Moose, Nautilus, Ocelot, Porpoise, Quail, Rabbit, Shark, Tiger, Urchin, Vipehttp://www.mysqlperformanceblog.com/2008/04/15/future-innodb-file-formats/Porpoise washed up near shipwreck prestontoday.netCrowds looked on after a porpoise was washed up [...]

]]> By: David Magda http://www.mysqlperformanceblog.com/2008/04/15/future-innodb-file-formats/comment-page-1/#comment-281938 David Magda Fri, 18 Apr 2008 22:50:10 +0000 http://www.mysqlperformanceblog.com/2008/04/15/future-innodb-file-formats/#comment-281938 Xeme. It's a type of gull. Xeme. It’s a type of gull.

]]> By: peter http://www.mysqlperformanceblog.com/2008/04/15/future-innodb-file-formats/comment-page-1/#comment-280567 peter Thu, 17 Apr 2008 18:14:36 +0000 http://www.mysqlperformanceblog.com/2008/04/15/future-innodb-file-formats/#comment-280567 I've asked Jay to change planetmysql.org to show MySQL Performance Blog instead of Peter Zaitsev. You also can report the bug if it does not passes author information from original feed - there are a lot of blogs by multiple authors. I’ve asked Jay to change planetmysql.org to show MySQL Performance Blog instead of Peter Zaitsev.

You also can report the bug if it does not passes author information from original feed – there are a lot of blogs by multiple authors.

]]> By: Yaroslav Vorozhko http://www.mysqlperformanceblog.com/2008/04/15/future-innodb-file-formats/comment-page-1/#comment-280117 Yaroslav Vorozhko Thu, 17 Apr 2008 11:39:20 +0000 http://www.mysqlperformanceblog.com/2008/04/15/future-innodb-file-formats/#comment-280117 >We should make Posted By more visible - this was done by Vadim :) At the google reader: Future InnoDB File Formats from Planet MySQL author: Peter Zaitsev At the Planet Mysql: Future InnoDB File Formats posted by Peter Zaitsev on Wed 16 Apr 2008 06:59 UTC So, i also think it was You post. :) Hmm, tt's very strange, becouse atom show correct author name: Vadim of this post. >We should make Posted By more visible – this was done by Vadim :)

At the google reader:
Future InnoDB File Formats
from Planet MySQL author: Peter Zaitsev

At the Planet Mysql:
Future InnoDB File Formats
posted by Peter Zaitsev on Wed 16 Apr 2008 06:59 UTC

So, i also think it was You post. :)

Hmm, tt’s very strange, becouse atom show correct author name: Vadim of this post.

]]> By: Jeremy Cole http://www.mysqlperformanceblog.com/2008/04/15/future-innodb-file-formats/comment-page-1/#comment-279738 Jeremy Cole Wed, 16 Apr 2008 21:37:47 +0000 http://www.mysqlperformanceblog.com/2008/04/15/future-innodb-file-formats/#comment-279738 According to the source, there are animals with X and Y: /* List of animal names representing file format. */ const char* file_format_name_map[] = { ... "Xenops", "Yak", ... }; According to the source, there are animals with X and Y:

/* List of animal names representing file format. */
const char* file_format_name_map[] = {
…
“Xenops”,
“Yak”,
…
};

]]> By: peter http://www.mysqlperformanceblog.com/2008/04/15/future-innodb-file-formats/comment-page-1/#comment-279734 peter Wed, 16 Apr 2008 21:29:41 +0000 http://www.mysqlperformanceblog.com/2008/04/15/future-innodb-file-formats/#comment-279734 Ken, We should make Posted By more visible - this was done by Vadim :) Ken,

We should make Posted By more visible – this was done by Vadim :)

]]> By: Ken Jacobs http://www.mysqlperformanceblog.com/2008/04/15/future-innodb-file-formats/comment-page-1/#comment-279567 Ken Jacobs Wed, 16 Apr 2008 17:48:33 +0000 http://www.mysqlperformanceblog.com/2008/04/15/future-innodb-file-formats/#comment-279567 Gnot Gnecessarily! Besides, Gazelles are fast and beautiful. Gnus ... well ... Gnot Gnecessarily!

Besides, Gazelles are fast and beautiful. Gnus … well …

]]> By: Kevin Burton http://www.mysqlperformanceblog.com/2008/04/15/future-innodb-file-formats/comment-page-1/#comment-279553 Kevin Burton Wed, 16 Apr 2008 17:30:03 +0000 http://www.mysqlperformanceblog.com/2008/04/15/future-innodb-file-formats/#comment-279553 This is kind of obvious but shouldn't Gazelle have been Gnu? http://en.wikipedia.org/wiki/Wildebeest Kevin This is kind of obvious but shouldn’t Gazelle have been Gnu?

http://en.wikipedia.org/wiki/Wildebeest

Kevin

]]> By: Stewart Smith http://www.mysqlperformanceblog.com/2008/04/15/future-innodb-file-formats/comment-page-1/#comment-279539 Stewart Smith Wed, 16 Apr 2008 17:07:11 +0000 http://www.mysqlperformanceblog.com/2008/04/15/future-innodb-file-formats/#comment-279539 Yabbie Yabbie

]]> By: Ken Jacobs http://www.mysqlperformanceblog.com/2008/04/15/future-innodb-file-formats/comment-page-1/#comment-279468 Ken Jacobs Wed, 16 Apr 2008 15:25:51 +0000 http://www.mysqlperformanceblog.com/2008/04/15/future-innodb-file-formats/#comment-279468 Indeed, Peter, the early adopter documentation and code (which is very slightly newer than what you tested) did incorporate Xenops and Yak! Indeed, Peter, the early adopter documentation and code (which is very slightly newer than what you tested) did incorporate Xenops and Yak!

]]>