Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Altas CLI does not seem to work with Postgres Aurora Limitless database #3353

Open
humerarehman opened this issue Jan 30, 2025 · 0 comments
Open
Assignees

Comments

@humerarehman
Copy link

Issue Summary
When using Atlas CLI to manage schema migrations with Amazon Aurora PostgreSQL Limitless, it fails due to database-specific limitations. Specifically, commands that require advisory locks or rely on certain PostgreSQL system catalogs do not function correctly.

Steps to Reproduce

  • Set up an Aurora PostgreSQL Limitless instance.
  • Configure Atlas CLI to connect to the database.
  • Run a schema migration or schema inspection command, such as:

atlas migrate apply --url "postgres://user:password@aurora-limitless-endpoint/postgres_limitless"

  • Observe the failure with errors related to advisory locks.

Expected Behavior
Atlas CLI should be able to:

  • Perform schema migrations without attempting pg_advisory_lock, which is not supported in Limitless mode.
  • Detect schema changes without depending on internal system tables that may be different in Aurora PostgreSQL Limitless.

Actual Behavior

Commands fail with errors such as:

ERROR: acquiring pg_advisory_lock is not supported in limitless database

Additional Details
Database Version: Amazon Aurora PostgreSQL 16.6-limitless
Atlas CLI Version: v0.29.1-ebcd381-canary

Suggested Fix or Workaround

  • Provide an option to disable advisory locks when using Aurora Limitless.
  • Allow specifying a separate database for schema tracking to work around Limitless database limitations.
  • Improve compatibility with Aurora Limitless-specific behaviours.

References
AWS Aurora PostgreSQL Limitless Documentation

@a8m a8m self-assigned this Jan 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants