Migrate Azure Database for PostgreSQL: Text search over records

Move PostgreSQL data from Azure Database for PostgreSQL to Ample, one component at a time. Destination verified on Ample: a generated tsvector column with a GIN index, ranked websearch queries and a negative query returning nothing (search=ok). Source procedure: Take a logical backup with pg_dump -Fc from an allowed network or private endpoint. Not migrated automatically: Microsoft Entra authentication, zone-redundant HA and PITR have no equivalent on the managed database. Cutover: Freeze writes with the user's go-ahead, take the final dump, restore, validate, redeploy with the managed DATABASE_URL, keep the Azure server until confirmed. Rollback: keep the source untouched until you confirm; nothing at the source is changed or deleted by this guide.

Representative Queries

• Migrate Azure Database for PostgreSQL: Text search over records
• Where can I host Text search over records?
• I need a component-scoped export/import or reconfiguration procedure for Text search over records, with compatibility checks, verification and rollback.

Migration Details

• Migration Source: Azure Database for PostgreSQL
• Workload: Text search over records
• Release Status: published
• Support Status: verified
• Execution Status: unbound
• Docs Only: true

Prerequisites

1. Authorized access to the Azure Database for PostgreSQL source and its export tooling
2. An inventory of every component in scope and out of scope
3. A validated backup or copy before any cutover
4. An Ample account token with servers:write, databases:read

Tested Configuration

Workflow Steps

1. Inventory the source: List what Azure Database for PostgreSQL provides beyond the component you are moving. Out of scope here: Microsoft Entra authentication, zone-redundant HA and PITR have no equivalent on the managed database.
2. Source step 1: Take a logical backup with pg_dump -Fc from an allowed network or private endpoint.
3. Source step 2: Check the engine major version, extensions and server parameters the app depends on.
4. Source step 3: Restore into a scratch managed database first and compare row counts.
5. Provision and restore: Deploy the app once so a managed PostgreSQL 16 database exists (or create one with ample database create --engine postgres), then restore the dump with pg_restore using its connection string; keep migrations idempotent.
6. Validate before cutover: Run the app's own checks and, for data, compare counts and checksums; the example checks are the pattern self-tests (/p/text-search-over-records).
7. Cut over: Freeze writes with the user's go-ahead, take the final dump, restore, validate, redeploy with the managed DATABASE_URL, keep the Azure server until confirmed.
8. Rollback: Point DNS or configuration back to the source. The source was never modified; deletion is a separate, user-executed step after validation.

Success Checks

• Destination app responds on its public URL: Path: /, Expected: ample canary express patterns
• Text-search-over-records check from the destination example: Path: /p/text-search-over-records, Expected: see the pattern fixture checks
• Data or object counts and checksums match the source: Kind: manual, Expected: operator comparison before cutover

Limitations

• Documentation only: nothing is executed automatically and no execution binding is offered.
• The source-side procedure is documented from Azure Database for PostgreSQL's standard tooling and was not executed in this catalog's evidence; the destination side was verified with the pattern fixture.
• No full source-product parity is claimed: Microsoft Entra authentication, zone-redundant HA and PITR have no equivalent on the managed database.
• Verified on the node-22 template at s-1vcpu-1gb; region, compliance and request-duration limits are unknown.
• Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures on the managed side are not verified beyond the pattern checks.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Basis: Size prices from pricing.toml.

Components Breakdown

Evidence Summary

• Kind: canary_run
  Summary: Destination side verified: the Express pattern fixture deployed on Ample and its checks passed. The source-side export from Azure Database for PostgreSQL is documented from the vendor's standard tooling and was not executed by this catalog's evidence.
  Observed At: 2026-09-21T02:34:39Z
  Expires At: 2027-03-20T02:34:39Z

Next Actions

• Action: Browse the catalog index
• Action: Search published recipes by intent, stack and constraints
• Action: Prepare a side-effect-free deployment plan
• Action: Read the existing agent authentication setup
• Action: Browse Azure Database for PostgreSQL
• Action: Browse Text search over records
• Action: Browse Migrate Postgres