Open
Description
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.
Metadata
Assignees
Labels
No labels
Activity