Migrate Google Cloud SQL for PostgreSQL: Text search over records

Move PostgreSQL data from Google Cloud SQL 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 through the Cloud SQL Auth Proxy or an authorized network. Not migrated automatically: Cloud SQL Auth Proxy/IAM authentication, high availability 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 Cloud SQL until confirmed. Rollback: keep the source untouched until you confirm; nothing at the source is changed or deleted by this guide.

Workload

Text search over records

Migration Source

Google Cloud SQL for PostgreSQL

Prerequisites

• Authorized access to the Google Cloud SQL for PostgreSQL source and its export tooling
• An inventory of every component in scope and out of scope
• A validated backup or copy before any cutover
• An Ample account token with servers:write, databases:read

Workflow Steps

1. Inventory the source
   List what Google Cloud SQL for PostgreSQL provides beyond the component you are moving. Out of scope here: Cloud SQL Auth Proxy/IAM authentication, high availability and PITR have no equivalent on the managed database.
2. Source step 1
   Take a logical backup with pg_dump -Fc through the Cloud SQL Auth Proxy or an authorized network.
3. Source step 2
   Check the engine major version, extensions and flags 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 Cloud SQL 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: expect ample canary express patterns
• text-search-over-records check from the destination example: expect see the pattern fixture checks
• data or object counts and checksums match the source: expect operator comparison before cutover

Limitations

• Documentation only: nothing is executed automatically and no execution binding is offered.
• The source-side procedure is documented from Google Cloud SQL 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: Cloud SQL Auth Proxy/IAM authentication, high availability 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
• Components:
  • app server: size s-1vcpu-1gb, quantity 1.0, monthlyAmount 5.0
  • managed PostgreSQL database: size s-1vcpu-1gb, quantity 1.0, monthlyAmount 5.0

Note

Destination always-on monthly price of the tested sizes; apps auto-pause when idle. Source costs are unknown to Ample.

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 Google Cloud SQL 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
  Implementation Revision: 1d28ae0-dirty (CLI 0.1.21) Expires At: 2027-03-20T02:34:39Z

Next Actions

• Browse the catalog index
  GET /v1/catalog
• Search published recipes by intent, stack and constraints
  POST /v1/catalog/search: { "limit": 5, "query": "Migrate Google Cloud SQL for PostgreSQL: Text search over records" }
• Prepare a side-effect-free deployment plan for an authorized project
  POST /v1/catalog/plan: { "inputs": {}, "projectId": "", "recipeId": "page:migrate:google-cloud-sql-for-postgresql:text-search-over-records", "recipeRevision": "r1" }
• Read the existing agent authentication setup
  GET /mcp/setup
• Browse Google Cloud SQL for PostgreSQL
  GET /v1/catalog/nodes/migration%3Agoogle-cloud-sql-for-postgresql
• Browse Text search over records
  GET /v1/catalog/nodes/pattern%3Atext-search-over-records
• Browse Migrate Postgres
  GET /v1/catalog/nodes/intent%3Amigrate-postgres