I Renamed a Hot Postgres Table Without Dropping a Request (opens in new tab)
Most table renames are database-easy and deploy-hard. The SQL looked trivial: ALTER TABLE oidc_clients RENAME TO oidc_provider_clients; In PostgreSQL, that rename is fast and metadata-only. The real problem was the rollout window around it. This was a live IAM service on the login path, deployed across multiple pods. During a rolling deploy, there is always a period where some instances run the new code and some still run the old code. During that window: new pods query oidc_provider_clients ...
Read the original article