# Baracuda innoDB file format question

**URL:** <https://forums.percona.com/t/baracuda-innodb-file-format-question/4107>\
**Category:** Other MySQL® Questions\
**Created:** [March 18, 2015, 12:52pm UTC](https://forums.percona.com/t/baracuda-innodb-file-format-question/4107 "2015-03-18T12:52:54Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![mikea730](https://avatars.discourse-cdn.com/v4/letter/m/e47c2d/32.png) [@mikea730](https://forums.percona.com/u/mikea730)\
**Post date:** [March 18, 2015, 12:52pm UTC](https://forums.percona.com/t/baracuda-innodb-file-format-question/4107/1 "2015-03-18T12:52:54Z")

</div>

When innodb\_file\_format is set to Baracuda, what change is actually happening? From what I read, if innodb\_file\_format is set to Baracuda, and new tables are created with the ROW\_FORMAT “Dynamic” or “Compressed” they will use the Baracuda file format. If the ROW\_FORMAT is set to “Compact” or “Redundant”, then the Antelope file format is used. When innodb\_file\_format is set to Baracuda, does that mean that the Baracuda file format is loaded in addition to Antelope so all 4 ROW\_FORMATS can be supported? Or does Baracuda also support the older Antelope ROW\_FORMATS? For new MySQL servers we build, I would like to set the innodb\_file\_format to Baracuda, but I want to make sure I understand how the older ROW\_FORMATS are supported.

UPDATE: sorry, I just noticed that I posted this in the Cloud forum. I meant to post in the “MySQL and Percona Server” forum.

Thanks,  
Mike