<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Gh-Ost on 黄文卓 | DevOps Engineer</title><link>https://socake.github.io/tags/gh-ost/</link><description>Recent content in Gh-Ost on 黄文卓 | DevOps Engineer</description><generator>Hugo -- gohugo.io</generator><language>zh-CN</language><managingEditor>17691281867@163.com (Wenzhuo Huang)</managingEditor><webMaster>17691281867@163.com (Wenzhuo Huang)</webMaster><copyright>© 2026 Wenzhuo Huang</copyright><lastBuildDate>Wed, 08 Jan 2025 10:00:00 +0800</lastBuildDate><atom:link href="https://socake.github.io/tags/gh-ost/index.xml" rel="self" type="application/rss+xml"/><item><title>数据库变更管理：从 gh-ost 到 Flyway 的完整工程化路径</title><link>https://socake.github.io/posts/database-change-management/</link><pubDate>Wed, 08 Jan 2025 10:00:00 +0800</pubDate><author>17691281867@163.com (Wenzhuo Huang)</author><guid>https://socake.github.io/posts/database-change-management/</guid><description>很多团队把&amp;quot;数据库变更管理&amp;quot;当成几条 SQL + 一个工单，实际上这是工程化程度最低的一块地方。一边是开发随手写 ALTER 把线上锁住，一边是 DBA 手动盯着进度条祈祷不出事。这篇文章把我总结的 DB 变更管理最佳实践分成工具、流程、组织三个层面讲，每一层都有可以直接落地的方案。</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://socake.github.io/posts/database-change-management/featured.jpg"/></item></channel></rss>