by bratao on 6/1/25, 1:24 AM with 42 comments
by nubinetwork on 6/1/25, 9:41 AM
by erulabs on 6/1/25, 2:59 AM
Maybe these optimizations can let me avoid moving to Vitess for another year!
by vasvir on 6/1/25, 5:49 AM
by femiagbabiaka on 6/1/25, 2:39 AM
EDIT: I missed that the authors wrote a GitHub book, including some descriptions of the problem(s): https://enhancedformysql.github.io/The-Art-of-Problem-Solvin...
Side note: One downside of ChatGPT generated documentation (assuming this was written in conjunction with an LLM) is that humans tend to be a little less verbose.
by ksec on 6/1/25, 7:31 AM
After how many years they have finally released 9.0 and are now at 9.3. I wonder how many of problem stated in the list is still true.
At least Vitess still get continuous development.
by mdaniel on 6/1/25, 3:24 AM
You know, a patch file can individually address each upsteam file it intends to modify, right? I presume someone who wants to casually read them would need to fork the repo, cut up the ginormous .patch file into the 2361 individual patches for ease of reading or deep-linking
I also just for-real don't understand how in the universe a ~15MB text file against an open source _git hosted_ project is a sane way of delivering value. Not a single time in the readme did they say why $(git diff origin/tags/8.0.42...HEAD > yolo.patch) was the chosen delivery mechanism
by lmz on 6/1/25, 2:41 AM
by santa_boy on 6/1/25, 2:06 AM
by orionblastar on 6/1/25, 1:48 AM