| *** ralonsoh__ is now known as ralonsoh | 13:36 | |
| fungi | gouthamr: heads up that https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/VR7XUI7V7QGFNHKFOXLFJJP6P4GGKOM3/ is requesting an addition to the agenda for the next tc meeting | 17:18 |
|---|---|---|
| fungi | the poster didn't include [tc] in the subject so just making sure you don't miss it | 17:18 |
| gouthamr | ah thanks for the heads up fungi | 17:19 |
| fungi | any time | 17:19 |
| gouthamr | it was on the next week's agenda - noonedeadpunk brought it up during open discussion last week | 17:19 |
| * gouthamr should hit save on the agenda edit! | 17:20 | |
| fungi | oh, right i recall seeing something related to it in the notes. so i guess it's worth a reply that the tc is already aware and actively discussing options | 17:20 |
| clarkb | that email talks a lot about utf8mb3. IMO part of any changes should involve moving to utf8mb4 if there is the possibility for 4 byte utf8 characters | 19:51 |
| fungi | it claimed ironic could not, due to (unspecified) internal design choices | 19:55 |
| clarkb | fungi: if I had to guess that is probably due to ironic having indexes on text columns and mariadb/mysql limit the total byte length of indexes to something like 768 | 19:56 |
| JayF | Ironic already made a fix | 19:56 |
| JayF | that sorta was around "make sure we do the right thing no matter what the default" | 19:57 |
| clarkb | I just don't want us to do a big effort to change the collation then 6 months later realize we need to change the type too | 19:57 |
| fungi | i mean it was claimed ironic could not use 4-byte utf8 in its databases | 19:57 |
| clarkb | it is likely to be less headache to do it together | 19:57 |
| fungi | not that ironic was unable to solve the general mariadb default change challenges | 19:58 |
| fungi | but why ironic is incompatible with 4-byte character encoding (if that's even true), i have no idea | 19:59 |
| clarkb | ya my hunch is the index byte width limit | 19:59 |
| clarkb | we've hit that with other systems migratiing to utf8mb4 and so far we've been able to update the indexes too in order to address it | 20:00 |
| JayF | https://docs.openstack.org/ironic/latest/install/install.html#set-up-the-database-for-bare-metal | 20:00 |
| JayF | First time I've ever read that lol | 20:00 |
| fungi | heh | 20:00 |
| clarkb | https://dev.mysql.com/doc/refman/8.4/en/innodb-limits.html | 20:02 |
| clarkb | apparently its 767 or 3072 bytes depending on the row format | 20:02 |
| JayF | https://opendev.org/openstack/ironic/commit/1435a15ce3013da0a3138e1c5ab6ac523c382bb8 | 20:03 |
| JayF | has a bit of detail | 20:03 |
| fungi | neat | 20:03 |
| clarkb | DYNAMIC is the default row format as of mysql 5.7.9 so 3072 is probably common | 20:03 |
| clarkb | I don't undersatnd that commit message. The field width is independent of byte size | 20:04 |
| JayF | clarkb: I just found the commit, I barely remembered it existing :) | 20:05 |
| clarkb | I suspect that varchar(255) * 3 = 765 < 767 and its actually the index limit I'm talking about not a limit to less than 255 4 byte chars | 20:05 |
| clarkb | you can varchar(255) all you want with utf8mb4 | 20:05 |
| clarkb | you can't put an index on that column if it is utf8mb4 and you are not using dynamic rows on innodb | 20:05 |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!