Remove CONCURRENTLY from migrations

[Weves]

Description

Seems to be causing all sorts of deadlocks and weirdness on cloud + not needed anymore since all large deployments have run this migration already.

How Has This Been Tested?

Ran migrations locally.

Backporting (check the box to trigger backport action)

Note: You have to check that the action passes, otherwise resolve the conflicts manually and tag the patches.

• This PR should be backported (make sure to check that the backport attempt succeeds)
• [Optional] Override Linear Check

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
internal-search	🔄 Building (Inspect)	Visit Preview	💬 Add feedback	Jun 28, 2025 6:59pm

[greptile-apps]

PR Summary

This PR removes the CONCURRENTLY keyword from index creation/deletion operations in migration scripts, with significant potential risks for new deployments.

• Migration 3bd4c84fe72f (dated 2025-02-26) has its CONCURRENTLY operations removed, which could cause table-locking and downtime for future deployments that haven't run these migrations
• The COMMIT statements critical for transaction management have been removed, which could lead to deadlocks in Postgres
• Removal of CONCURRENTLY from GIN index operations in 495cb26ce93e is particularly concerning as GIN indexes are typically resource-intensive to build
• The PR's justification that "all large deployments have run this migration" doesn't account for new deployments, test environments, or future database rebuilds

_{2 files reviewed, no comments
Edit PR Review Bot Settings | Greptile}