Skip to content

Comment on Schema changes and the Postgres lock queue

Comments

So how do people handle this in practice if the users table in this example has a ton of traffic? It might not ever succeed even with exponential backoff. It also seems strange that Postgres would need to lock the entire table just to add a new column.

Set a short timeout on lock acquisition, eventually it will get through or you have to tolerate a larger timeout

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.