<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>数据库 on BvBeJ的小站</title><link>https://www.bvbej.com/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/</link><description>Recent content in 数据库 on BvBeJ的小站</description><generator>Hugo</generator><language>zh-CN</language><lastBuildDate>Sat, 16 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.bvbej.com/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/feed.xml" rel="self" type="application/rss+xml"/><item><title>Kubernetes StatefulSet 升级：有状态服务发布策略</title><link>https://www.bvbej.com/posts/kubernetes-statefulset-upgrade/</link><pubDate>Sat, 16 May 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/kubernetes-statefulset-upgrade/</guid><description>有状态组件升级要把数据一致性放在第一位</description></item><item><title>PostgreSQL 表膨胀治理：VACUUM、索引重建与窗口规划</title><link>https://www.bvbej.com/posts/postgres-vacuum-bloat-control/</link><pubDate>Sat, 16 May 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/postgres-vacuum-bloat-control/</guid><description>写多读多场景下，膨胀管理决定了查询稳定性与存储成本。</description></item><item><title>Go 数据库事务重试：何时该重试，何时应失败</title><link>https://www.bvbej.com/posts/go-db-transaction-retry/</link><pubDate>Thu, 14 May 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/go-db-transaction-retry/</guid><description>重试策略必须和幂等语义一起设计</description></item><item><title>Go 服务零停机数据库 Schema 迁移实战</title><link>https://www.bvbej.com/posts/go-zero-downtime-schema-migration/</link><pubDate>Mon, 27 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/go-zero-downtime-schema-migration/</guid><description>把 DDL 变更拆成可回滚、可观测、可灰度的迁移链路，避免高峰期雪崩。</description></item><item><title>Rust 异步数据库访问：连接池、超时与稳定性</title><link>https://www.bvbej.com/posts/rust-async-db-pool/</link><pubDate>Thu, 16 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/rust-async-db-pool/</guid><description>异步访问数据库不只是把函数改成 async，更关键的是控制连接、等待时间和失败路径</description></item></channel></rss>