Craig Kerstiens • 10/1/2014

A simple guide for DB migrations

Read Original

This article explains a common pitfall in PostgreSQL: adding a NOT NULL constraint to a new column can rewrite the entire table and cause downtime. It provides a step-by-step, safer migration strategy: first add the column as nullable with a default, then backfill values in a background job, and finally add the NOT NULL constraint to ensure application uptime.

0 comments
#performance optimization #postgresql #Database Migrations
A simple guide for DB migrations

Comments

No comments yet

Be the first to share your thoughts!

Browser Extension

Get instant access to AllDevBlogs from your browser

Top of the Week

1
The Beautiful Web
Jens Oliver Meiert • 2 votes
2
When your coding agent doesn’t understand your project, you’ll get junk
Benjamin Cane • 1 votes
3
LLM Use in the Python Source Code
Miguel Grinberg • 1 votes
4
Wagon’s algorithm in Python
John D. Cook • 1 votes
5
An example conversation with Claude Code
Dumm Zeuch • 1 votes