# Navigating PostgreSQL Locks with Neon and Atlas

DevFeed: [Navigating PostgreSQL Locks with Neon and Atlas](<https://devfeed.tech/articles/navigating-postgresql-locks-with-neon-and-atlas-5733.md>)

Original publisher: [Read original article](<https://neon.com/blog/postgres-locks-neon-atlas>)

Author: Rotem Tamir

Published: 2025-03-14T18:26:07Z

Content type: article

Language: en

Sources: [Blog -- Neon Docs](<https://devfeed.tech/sources/blog-neon-docs.md>)

Topics: [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [Database Migration](<https://devfeed.tech/topics/database-migration.md>), [Database](<https://devfeed.tech/topics/database.md>), [Back end](<https://devfeed.tech/topics/backend.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [backend](<https://devfeed.tech/tags/backend.md>), [community](<https://devfeed.tech/tags/community.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [database](<https://devfeed.tech/tags/database.md>), [locking](<https://devfeed.tech/tags/locking.md>), [migrations](<https://devfeed.tech/tags/migrations.md>), [performance](<https://devfeed.tech/tags/performance.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [schema](<https://devfeed.tech/tags/schema.md>)

## AI overview

The article explains how PostgreSQL schema migrations can acquire long-running locks and cause production outages. It uses a uniqueness-constraint example and describes creating and validating a unique index before attaching the constraint to reduce blocking.

## Source excerpt

As applications evolve, making changes to your database schema is inevitable, whether you're adding indexes to keep performance up with a growing user base or adding new features to an existing product. Most of the time, these schema migrations will go smoothly, but if you're not...