<?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>Databases on Allen Ziegenfus</title><link>https://allenz.net/tags/databases/</link><description>Recent content in Databases on Allen Ziegenfus</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 16 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://allenz.net/tags/databases/index.xml" rel="self" type="application/rss+xml"/><item><title>Environment-stable table ownership: surviving cross-environment restore with IAM database auth</title><link>https://allenz.net/writing/environment-stable-table-ownership-surviving-cross-environment-restore-with-iam-database-auth/</link><pubDate>Sat, 16 May 2026 00:00:00 +0000</pubDate><guid>https://allenz.net/writing/environment-stable-table-ownership-surviving-cross-environment-restore-with-iam-database-auth/</guid><description>Cloud SQL IAM database auth breaks cross-environment restores because table ownership encodes a per-environment service account. Make ownership environment-independent by owning every table as cloudsqlsuperuser.</description></item><item><title>Stable vs. rewritten identity: cross-environment database restore in a stateful platform</title><link>https://allenz.net/writing/stable-vs.-rewritten-identity-cross-environment-database-restore-in-a-stateful-platform/</link><pubDate>Fri, 15 May 2026 00:00:00 +0000</pubDate><guid>https://allenz.net/writing/stable-vs.-rewritten-identity-cross-environment-database-restore-in-a-stateful-platform/</guid><description>When a platform bakes an environment-derived identity into its database on first boot, restoring across environments crash-loops on a mismatch. The fix is a product question: stabilize the identity, or rewrite it after restore?</description></item></channel></rss>