Project ideas from Hacker News discussions.

Is your Postgres migration safe or not safe?

📝 Discussion Summary (Click to expand)

Theme 1 – Mitigating lock contention with lock_timeout and retries

"Thing that bit me most wasn't the DDL itself, it was lock queuing. An ADD COLUMN is instant but if it waits behind a long read, every query behind it piles up too. Lock_timeout plus retry saved us more than any clever migration tool." — kettlecrisp99
"Agree. lock_timeout will go a long way in terms of damage control." — vira28

Theme 2 – Browser‑based, WASM‑powered static analysis for early migration safety

"really like the browser‑only approach here - catching the obvious migration risks locally before they ever reach CI feels super useful" — rohansx
"Adding some context… I tried to explain the internals of how the locking (rewrite) works… but I realized most of the devs just want the answer - Is it safe or not safe to run?" — vira28 (author of the safe‑not‑safe tool)

Theme 3 – Need for nuanced safety profiles and deeper integration (CI/CLI or runtime state)

"Currently, it's very binary. The answer is more nuanced and it should classify it based on the profiles like you mentioned." — necovek
"These kinds of rule‑based migration safety checks are simple, but hardly complete…. Safety also depends on the size/activity of a table being altered…" — orf
"If you continue working on this a good direction to go in would be to package it as a command line tool, so it can be integrated into testing and release processes." — paol


🚀 Project Ideas

Generating project ideas…

Gathering the best ideas from the HN discussion…

Read Later