Migrate Google Cloud SQL for PostgreSQL: JSON document metadata · Ample Computer

Migrate Google Cloud SQL for PostgreSQL: JSON document metadata

Move PostgreSQL data from Google Cloud SQL for PostgreSQL to Ample, one component at a time. Destination verified on Ample: a jsonb column with a GIN index queried by path and containment, with an aggregate over matching documents (json=ok). Source procedure: Take a logical backup with pg_dump -Fc through the Cloud SQL Auth Proxy or an authorized network. Move separately: Cloud SQL Auth Proxy/IAM authentication, high availability and PITR are Cloud SQL features; on Ample the app connects with injected credentials and backs up with pg_dump. 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.

What it runs on

You need

Exact tested configuration

Steps

  1. Inventory the source. List what Google Cloud SQL for PostgreSQL provides beyond the component you are moving. Plan these separately: Cloud SQL Auth Proxy/IAM authentication, high availability and PITR are Cloud SQL features; on Ample the app connects with injected credentials and backs up with pg_dump.

  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.

   $ ample database create --name <db-name> --engine postgres
  1. 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/json-document-metadata).

  2. 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.

  3. Rollback. Point DNS or configuration back to the source. The source was never modified; deletion is a separate, user-executed step after validation.

How it was checked

✓ destination app responds on its public URL· http get/ → “ample canary express patterns”
✓ json-document-metadata check from the destination example· http get/p/json-document-metadata → “see the pattern fixture checks”
✓ data or object counts and checksums match the source· manual → “operator comparison before cutover”

Evidence

  1. November 5, 2026 · canary run
    Destination side verified: the Express pattern fixture deployed on Ample (npm install, npm run build --if-present, npm run start on the node-22 template) and its checks passed (a jsonb column with a GIN index queried by path and containment, with an aggregate over matching documents (json=ok)). The source-side export from Google Cloud SQL for PostgreSQL uses the vendor's standard tooling.

Tested examples

What it doesn’t cover