I Renamed a Hot Postgres Table Without Dropping a Request (opens in new tab)

Covered by 3 sources See all sources covering this story including GitHub, ZennDiscussed on DEV

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
Sign in to keep reading the full article.

Covered in 3 articles

GitHub·
Feeds

In other languages

Zenn·
Feeds
habr.com·
Feeds

Keyboard Shortcuts

Navigation

Next / previous post
j/k
Open post
oorEnter
Preview post
v

Post Actions

Love post
a
Like post
l
Dislike post
d
Undo reaction
u
Save / unsave
s

Recommendations

Add interest / feed
Enter
Not interested
x

Go to

Home
gh
Interests
gi
Feeds
gf
Likes
gl
History
gy
Changelog
gc
Settings
gs
Discover
gb
Search
/

General

Show this help
?
Submit feedback
!
Close modal / unfocus
Esc

Press ? anytime to show this help