<?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>Postgresql on Wilson Wu</title><link>https://wilsonwu.me/en/tags/postgresql/</link><description>Recent content in Postgresql on Wilson Wu</description><generator>Hugo -- 0.127.0</generator><language>en-US</language><lastBuildDate>Thu, 13 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://wilsonwu.me/en/tags/postgresql/index.xml" rel="self" type="application/rss+xml"/><item><title>OpenWebUI Database Migration in Practice: Smoothly Migrating from Self-Hosted PostgreSQL on a VM to Azure Database for PostgreSQL</title><link>https://wilsonwu.me/en/blog/2026/migrate-openwebui-to-azure-pg/</link><pubDate>Thu, 13 Aug 2026 00:00:00 +0000</pubDate><guid>https://wilsonwu.me/en/blog/2026/migrate-openwebui-to-azure-pg/</guid><description>As the volume of users, conversations, files, and knowledge base data in OpenWebUI continued to grow, the self-hosted PostgreSQL instance on an Azure VM created an increasing operational burden, including database patching, backups, disaster recovery, storage monitoring, and security maintenance.
To reduce maintenance costs and improve database reliability, I migrated the OpenWebUI application database from PostgreSQL running locally on the VM to Azure Database for PostgreSQL Flexible Server.
This migration used the following approach:</description></item></channel></rss>