이 페이지에는 유지보수 변경 로그가 포함되어 있습니다.
Cloud SQL은 정기적으로 유지보수 업데이트를 출시합니다. 유지보수 업데이트에는 새로운 기능, 보안 패치, 버그 수정, 성능 개선 등과 같은 내용이 포함됩니다.
유지보수 업데이트는 셀프서비스 유지보수를 사용하거나 Cloud SQL에서 몇 개월마다 1회 수행되는 예약 유지보수 업데이트를 통해 수행될 수 있습니다. 예약 유지보수 업데이트의 경우 유지보수 업데이트가 수행되는 기간을 설정할 수 있습니다. 유지보수 기간 보기 및 설정을 참조하세요.
유지보수 업데이트에 대해 자세히 알아보려면 Cloud SQL 인스턴스의 유지보수 업데이트를 참조하세요.
제공된 최신 유지보수 변경사항을 가져오려면 https://cloud.google.com/feeds/cloud-sql-mysql-8-4-maintenance-changelog.xml
URL을 피드 리더에 추가합니다.
MYSQL_8_4_6.R20250531.01_23
출시일 | 출시 유형 | 데이터베이스 부 버전 |
---|---|---|
2025-09-22 | 새 버전 | MySQL 8.4.6 |
보안 패치
데이터베이스
CVE-2025-50085, CVE-2025-50077, CVE-2025-50088, CVE-2025-50092, CVE-2025-50099, CVE-2025-50077, CVE-2025-53023, CVE-2025-50087, CVE-2025-50096, CVE-2025-50086, CVE-2025-50093, CVE-2025-50094, CVE-2025-50104, CVE-2025-50076, CVE-2025-50078, CVE-2025-50082, CVE-2025-50083, CVE-2025-50079, CVE-2025-50084, CVE-2025-50087, CVE-2025-50089, CVE-2025-50091, CVE-2025-50095, CVE-2025-50101, CVE-2025-53032, CVE-2025-50102, CVE-2025-50098, CVE-2024-37891, CVE-2025-5399, CVE-2025-53023, CVE-2025-50097, CVE-2025-50081, CVE-2025-50081, CVE-2025-50103, CVE-2025-50080
운영체제
CVE-2021-33503, CVE-2023-43804, CVE-2023-45803, CVE-2023-50782, CVE-2024-11584, CVE-2024-34397, CVE-2024-47081, CVE-2024-52533, CVE-2024-6174, CVE-2025-1153, CVE-2025-27613, CVE-2025-27614, CVE-2025-46835, CVE-2025-48384, CVE-2025-48385, CVE-2025-5244, CVE-2025-5245, CVE-2025-7545, CVE-2025-7546, CVE-2025-8224, CVE-2025-8225
기타 패치
- MySQL 8.4 부 버전이 MySQL 8.4.6으로 업데이트됩니다.
- 버그 #118888을 완화하기 위해 빠른 실패 메커니즘을 구현했습니다. 이 변경사항은 MySQL이 무한 루프에 진입하여 모든 디스크 공간을 소진하는 것을 방지합니다. 이제 MySQL에서 조치를 취할 수 있는 다음 오류를 즉시 보고합니다. ERROR HY000: Internal error: Per-thread DDL buffer is too small. --innodb_ddl_buffer_size를 늘리거나 --innodb_parallel_read_threads를 줄이는 것이 좋습니다.
MYSQL_8_4_5.R20250531.01_15
출시일 | 출시 유형 | 데이터베이스 부 버전 |
---|---|---|
2025-08-18 | 셀프서비스 | MySQL 8.4.5 |
보안 패치
CVE-2016-1585, CVE-2024-11053, CVE-2024-23653, CVE-2024-26130, CVE-2024-41110, CVE-2024-43840, CVE-2024-48615, CVE-2024-50349, CVE-2024-52006, CVE-2024-53427, CVE-2024-58070, CVE-2024-58083, CVE-2025-0167, CVE-2025-1181, CVE-2025-1215, CVE-2025-1365, CVE-2025-1371, CVE-2025-1372, CVE-2025-1377, CVE-2025-1632, CVE-2025-21853, CVE-2025-21867, CVE-2025-21887, CVE-2025-21962, CVE-2025-21980, CVE-2025-21997, CVE-2025-22134, CVE-2025-22870, CVE-2025-23266, CVE-2025-23267, CVE-2025-24014, CVE-2025-26603, CVE-2025-27423, CVE-2025-29087, CVE-2025-29768, CVE-2025-3198, CVE-2025-32414, CVE-2025-32415, CVE-2025-32462, CVE-2025-32463, CVE-2025-32728, CVE-2025-4598, CVE-2025-46836, CVE-2025-47273, CVE-2025-48060, CVE-2025-5914, CVE-2025-6965
MYSQL_8_4_5.R20250531.01_14
출시일 | 출시 유형 | 데이터베이스 마이너 버전 |
---|---|---|
2025-07-28 | 셀프서비스 | MySQL 8.4.5 |
보안 패치
이 유지보수 업데이트와 관련된 보안 패치는 없습니다.
MYSQL_8_4_5.R20250531.01_10
출시일 | 출시 유형 | 데이터베이스 마이너 버전 |
---|---|---|
2025-07-20 | 자동 유지보수 | MySQL 8.4.5 |
보안 패치
이 유지보수 업데이트와 관련된 보안 패치는 없습니다.
MYSQL_8_4_5.R20250304.00_05
출시일 | 출시 유형 | 데이터베이스 마이너 버전 |
---|---|---|
2025-05-30 | 새 버전 | MySQL 8.4.5 |
보안 패치
CVE-2025-21577, CVE-2025-30682, CVE-2025-30687, CVE-2025-30688, CVE-2025-21574, CVE-2025-21575, CVE-2025-30722, CVE-2025-30693, CVE-2025-30695, CVE-2025-30715, CVE-2025-21584, CVE-2025-21580, CVE-2025-21588, CVE-2025-21581, CVE-2025-21585, CVE-2025-30689, CVE-2025-21579, CVE-2025-30696, CVE-2025-30705, CVE-2025-30683, CVE-2025-30684, CVE-2025-30685, CVE-2025-30699, CVE-2025-30704, CVE-2025-30721, CVE-2025-30703, CVE-2025-30681
MYSQL_8_4_4.R20250304.00_03
출시일 | 출시 유형 | 데이터베이스 마이너 버전 |
---|---|---|
2025-05-12 | 셀프서비스 | MySQL 8.4.4 |
보안 패치
CVE-2022-2289, CVE-2024-57951, CVE-2024-8176, CVE-2024-9287, CVE-2025-21785, CVE-2025-21791, CVE-2025-21858, CVE-2025-21863, CVE-2025-27113
MYSQL_8_4_4.R20250304.00_01
출시일 | 출시 유형 | 데이터베이스 마이너 버전 |
---|---|---|
2025-03-06 | 새 버전 | MySQL 8.4.4 |
보안 패치
CVE-2024-23653, CVE-2024-47745, CVE-2024-49861, CVE-2024-49996, CVE-2024-50047, CVE-2024-50055, CVE-2024-50067, CVE-2024-50121, CVE-2024-50164, CVE-2024-50186, CVE-2024-50275, CVE-2024-53096, CVE-2024-53099, CVE-2024-53141, CVE-2024-53142, CVE-2024-53166, CVE-2024-53168, CVE-2024-53170, CVE-2024-53173, CVE-2024-53179, CVE-2024-53206, CVE-2024-56600, CVE-2024-56601, CVE-2024-56606, CVE-2024-56614, CVE-2024-56615, CVE-2024-56635, CVE-2024-56658, CVE-2024-56664, CVE-2024-56672, CVE-2025-0840, CVE-2025-21490, CVE-2025-21491, CVE-2025-21492, CVE-2025-21493, CVE-2025-21494, CVE-2025-21497, CVE-2025-21499, CVE-2025-21500, CVE-2025-21501, CVE-2025-21503, CVE-2025-21504, CVE-2025-21505, CVE-2025-21518, CVE-2025-21519, CVE-2025-21520, CVE-2025-21522, CVE-2025-21523, CVE-2025-21525, CVE-2025-21529, CVE-2025-21531, CVE-2025-21534, CVE-2025-21536, CVE-2025-21540, CVE-2025-21546, CVE-2025-21555, CVE-2025-21559, CVE-2025-21566, CVE-2025-21567, CVE-2025-21631, CVE-2025-21652
MYSQL_8_4_3.R20241208.01_04
출시일 | 출시 유형 | 데이터베이스 부 버전 |
---|---|---|
2025-02-07 | 셀프서비스 | MySQL 8.4.3 |
보안 패치
CVE-2024-47682, CVE-2024-47685, CVE-2024-47696, CVE-2024-47701, CVE-2024-47727, CVE-2024-47742, CVE-2024-48957, CVE-2024-48958, CVE-2024-49860, CVE-2024-49882, CVE-2024-49883, CVE-2024-49884, CVE-2024-49889, CVE-2024-49936, CVE-2024-49967, CVE-2024-49983, CVE-2024-50033, CVE-2024-50035, CVE-2024-50036, CVE-2024-50083, CVE-2024-50115, CVE-2024-50131, CVE-2024-50143, CVE-2024-50151, CVE-2024-50154, CVE-2024-50228, CVE-2024-50257, CVE-2024-50262, CVE-2024-50264, CVE-2024-50278, CVE-2024-50279, CVE-2024-53057, CVE-2024-53082, CVE-2024-53168, CVE-2024-53179, CVE-2024-56664, CVE-2025-21631
MYSQL_8_4_3.R20241208.01_00
출시일 | 출시 유형 | 데이터베이스 부 버전 |
---|---|---|
2024-12-10 | 자동 유지보수 | MySQL 8.4.3 |
보안 패치
CVE-2024-0132, CVE-2024-0133, CVE-2024-46744, CVE-2024-46750, CVE-2024-46763, CVE-2024-46679, CVE-2024-46721, CVE-2024-46800, CVE-2024-46743, CVE-2024-46738, CVE-2024-43817, CVE-2024-44947, CVE-2024-45025, CVE-2024-41012, CVE-2024-45018, CVE-2024-45022, CVE-2024-45021, CVE-2024-44940, CVE-2024-46686, CVE-2007-4559, CVE-2023-27043, CVE-2024-7592, CVE-2024-6232, CVE-2024-6119, CVE-2024-45492, CVE-2024-45490, CVE-2024-45491, CVE-2024-44983, CVE-2024-43893, CVE-2024-44944, CVE-2024-43871, CVE-2024-44989, CVE-2024-44990, CVE-2024-45000, CVE-2024-42307, CVE-2024-43914, CVE-2024-43873, CVE-2024-43882, CVE-2024-44985, CVE-2024-44986, CVE-2023-7256, CVE-2024-44987, CVE-2024-43889, CVE-2024-42302, CVE-2024-41057, CVE-2024-43837, CVE-2024-43855, CVE-2024-41076, CVE-2024-42316, CVE-2024-43828, CVE-2024-43856, CVE-2024-41073, CVE-2024-44934, CVE-2024-37370, CVE-2024-37371, CVE-2023-46246, CVE-2024-41957, CVE-2024-41965, CVE-2024-41058, CVE-2024-43854, CVE-2024-43854, CVE-2024-41098, CVE-2024-42270, CVE-2023-52889, CVE-2024-42283, CVE-2024-42268, CVE-2024-42269, CVE-2024-42285, CVE-2024-6602, CVE-2024-6345, CVE-2024-2511, CVE-2024-4603, CVE-2024-4741, CVE-2024-5535, CVE-2024-7264, CVE-2024-39472, CVE-2024-6197, CVE-2024-6345, CVE-2021-36084, CVE-2021-36085, CVE-2021-36086, CVE-2021-36087, CVE-2024-39894, CVE-2024-36891
MYSQL_8_4_3.R20241024.00_02
출시일 | 출시 유형 | 데이터베이스 마이너 버전 |
---|---|---|
2024-12-05 | 셀프서비스 | MySQL 8.4.3 |
보안 패치
CVE-2024-21230, CVE-2024-21194, CVE-2024-21199, CVE-2024-21207, CVE-2024-21218, CVE-2024-21236, CVE-2024-21239, CVE-2024-21198, CVE-2024-21219, CVE-2024-21203, CVE-2024-21197, CVE-2024-21200, CVE-2024-21201, CVE-2024-21241, CVE-2024-21193, CVE-2024-21204, CVE-2024-21212, CVE-2024-21213, CVE-2024-21231, CVE-2024-21232, CVE-2024-21243, CVE-2024-21244
MYSQL_8_4_0.R20241020.00_00
출시일 | 출시 유형 | 데이터베이스 부 버전 |
---|---|---|
2024-10-25 | 셀프서비스 | MySQL 8.4.0 |
보안 패치
CVE-2024-36979, CVE-2024-37370, CVE-2024-37371, CVE-2024-37407, CVE-2024-38538, CVE-2024-38555, CVE-2024-38577, CVE-2024-39463, CVE-2024-39487, CVE-2024-40906, CVE-2024-40954, CVE-2024-40958, CVE-2024-40994, CVE-2024-41000, CVE-2024-41049, CVE-2024-41058, CVE-2024-41073, CVE-2024-41087, CVE-2024-42154, CVE-2024-42285, CVE-2024-42302, CVE-2024-43873, CVE-2024-43882, CVE-2024-44934, CVE-2024-44985, CVE-2024-44986, CVE-2024-44987, CVE-2024-45490, CVE-2024-45491, CVE-2024-45492, CVE-2024-46738, CVE-2024-46800, CVE-2024-6197, CVE-2024-6232, CVE-2024-7592