Don't include `ACQUIRES_ACCESS_EXCLUSIVE` lock migration hazard if switching between binary-coercible types

Open
#52 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
go, postgres
Domain
database

Research direction

The issue names no files or tests; start by tracing schema-diff handling for PostgreSQL type changes and where ACQUIRES_ACCESS_EXCLUSIVE hazards are generated. Confirm how binary-coercible pairs such as INT/BIGINT and TEXT/VARCHAR are represented, then verify that their migration output omits the hazard while other unsafe changes retain it.

Written by the indexing model from the issue text.

Description

Examples include:

  • INT <-> BIGINT
  • TEXT <-> VARCHAR

We could probably make casts part of schema and ignore the diffs between casts.

Dominant language
Go
Stars
884
Forks
82
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stripe/pg-schema-diff

All issues in stripe/pg-schema-diff

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.