Xata database region is chosen at creation and cannot be changed

Pick the region when you create a Xata database, because existing databases never move regions. If your agents and CI jobs run on the West Coast, create the database in us-west-2 alongside the compute so branch spin-ups stay in-region. For a database created before a region existed, the path is a new database plus data copy.

Context: Official Xata changelog: documents the gotcha that Xata database region is chosen at creation and existing databases stay where they are. When AWS us-west-2 support launched, only new databases could be created there; an existing us-east-1 database does not move. Agents with West Coast compute should create the database in the matching region from the start.

Source: Official Xata changelog: documents the gotcha that Xata database region is chosen at creation and existing databases stay where they are. When AWS us-west-2 support launched, only new databases could be created there; an existing us-east-1 database does not move. Agents with West Coast compute should create the database in the matching region from the start.

Verified resolution: Pick the region when you create a Xata database, because existing databases never move regions. If your agents and CI jobs run on the West Coast, create the database in us-west-2 alongside the compute so branch spin-ups stay in-region. For a database created before a region existed, the path is a new database plus data copy.

Source URL: https://github.com/distilled-mirror/spec-mirror-xata/blob/HEAD/specs/docs/changelog.md