M

MySQL Server

M
MySQL Server Database v9.7.2

mysql-9.7.2: Bug#39724798 Streamline GitHub contribution automation

Problem: The GitHub contribution path lacked consistent intake templates, shared local CI entry points, and automated build, test, formatting, ownership, and triage feedback. Pull requests could also define workflow changes that executed before those definitions were merged into trunk. The selected-actions policy prevented the external Codex action from running. Solution: Add structured issue and…

M
MySQL Server Database v9.7.2

mysql-cluster-9.7.2: Bug#39724798 Streamline GitHub contribution automation

Problem: The GitHub contribution path lacked consistent intake templates, shared local CI entry points, and automated build, test, formatting, ownership, and triage feedback. Pull requests could also define workflow changes that executed before those definitions were merged into trunk. The selected-actions policy prevented the external Codex action from running. Solution: Add structured issue and…

M
MySQL Server Database v26.7.0

mysql-26.7.0: Bug#39724798 Streamline GitHub contribution automation

Problem: The GitHub contribution path lacked consistent intake templates, shared local CI entry points, and automated build, test, formatting, ownership, and triage feedback. Pull requests could also define workflow changes that executed before those definitions were merged into trunk. The selected-actions policy prevented the external Codex action from running. Solution: Add structured issue and…

M
MySQL Server Database v26.7.0

mysql-cluster-26.7.0: Bug#39724798 Streamline GitHub contribution automation

Problem: The GitHub contribution path lacked consistent intake templates, shared local CI entry points, and automated build, test, formatting, ownership, and triage feedback. Pull requests could also define workflow changes that executed before those definitions were merged into trunk. The selected-actions policy prevented the external Codex action from running. Solution: Add structured issue and…

M
MySQL Server Database v8.4.11

mysql-8.4.11

Bug#39249507 Regression : "Row size too large (> 8126)" error with ta…

M
MySQL Server Database v8.4.10

mysql-8.4.10

Bug#39204635 - Unauthenticated repeated X Protocol TLS upgrade crashe…

M
MySQL Server Database v9.7.1

mysql-9.7.1

Bug#39204635 - Unauthenticated repeated X Protocol TLS upgrade crashe…

M
MySQL Server Database v9.7.0

mysql-9.7.0: Bug#39129182 Mysqld Crash due to "Deadlock Detected!" Error

Symptom: A deadlock between thread performing a typical dive into B-tree, and a thread trying to physically remove a record could happen, in case the later had to perform merge with a sibling requiring deregistering one of the children from their parents, which in turn required X-latching the parent while holding X-latch on a child. Analysis: The most typical latching order in the B-tree (simplify…

M
MySQL Server Database v9.7.0

mysql-cluster-9.7.0: Bug#39129182 Mysqld Crash due to "Deadlock Detected!" Error

Symptom: A deadlock between thread performing a typical dive into B-tree, and a thread trying to physically remove a record could happen, in case the later had to perform merge with a sibling requiring deregistering one of the children from their parents, which in turn required X-latching the parent while holding X-latch on a child. Analysis: The most typical latching order in the B-tree (simplify…

M
MySQL Server Database v8.4.9

mysql-8.4.9: Bug#39129182 Mysqld Crash due to "Deadlock Detected!" Error

Symptom: A deadlock between thread performing a typical dive into B-tree, and a thread trying to physically remove a record could happen, in case the later had to perform merge with a sibling requiring deregistering one of the children from their parents, which in turn required X-latching the parent while holding X-latch on a child. Analysis: The most typical latching order in the B-tree (simplify…

M
MySQL Server Database v8.4.9

mysql-cluster-8.4.9: Bug#39129182 Mysqld Crash due to "Deadlock Detected!" Error

Symptom: A deadlock between thread performing a typical dive into B-tree, and a thread trying to physically remove a record could happen, in case the later had to perform merge with a sibling requiring deregistering one of the children from their parents, which in turn required X-latching the parent while holding X-latch on a child. Analysis: The most typical latching order in the B-tree (simplify…

M
MySQL Server Database v8.0.46

mysql-cluster-8.0.46: Bug#39129182 Mysqld Crash due to "Deadlock Detected!" Error

Symptom: A deadlock between thread performing a typical dive into B-tree, and a thread trying to physically remove a record could happen, in case the later had to perform merge with a sibling requiring deregistering one of the children from their parents, which in turn required X-latching the parent while holding X-latch on a child. Analysis: The most typical latching order in the B-tree (simplify…