Google Cloud Spanner to PostgreSQL integration

Connect Google Cloud Spanner to PostgreSQL and automatically sync your application data. Weld extracts data from Google Cloud Spanner, loads it into PostgreSQL, and lets you transform the data using SQL or dbt, no custom scripts required.

4.8 on G2
Image not found!
Source
WeldWeld
PostgreSQLWarehouse
Weld · New sync
Image not found!
SourceGoogle Cloud SpannerConnected
Tables to sync

Your own tables, picked when you set up the sync.

  • Extract
  • Load
  • Keep in sync
PostgreSQLDestinationPostgreSQLReady
spanner schema
  • spanner.Synced
  • spanner.Syncing
  • spanner.Synced
  • spanner.Synced

Trusted by data and AI teams

  • Flatpay
  • Holafly
  • eComplete
  • Dishoom
  • Danish Endurance
  • Female Invest
  • Son of a Tailor
  • Onomondo
  • Medik8
  • Pas Normal Studios
How it works

How to set up Google Cloud Spanner to PostgreSQL in Weld.
In the app, with the API or an agent.

Weld · New Google Cloud Spanner sync
GNew connectionGoogle Cloud SpannerAuthorised
Connection namespanner
AuthorizeOpens Google Cloud Spanner to grant read access
Use cases

Why sync Google Cloud Spanner to PostgreSQL?
Ready for analysis.

Centralizing your Google Cloud Spanner data in PostgreSQL lets you join it with other data sources for cross-platform analytics and deeper insights.

Build reliable dashboards and reports by querying Google Cloud Spanner data directly in PostgreSQL using SQL or your preferred BI tool.

  • Centralized data warehouse

    Bring Google Cloud Spanner data into PostgreSQL alongside other sources to create a single source of truth for your organization.

  • Automated reporting

    Replace manual exports and spreadsheet-based reporting with automated pipelines from Google Cloud Spanner to PostgreSQL. Connect BI tools like Looker, Metabase, or Power BI.

Data

What data can you sync?
From Google Cloud Spanner to PostgreSQL.

Weld syncs the objects the Google Cloud Spanner connector exposes into PostgreSQL, and you choose which tables and fields to include. The connector's docs list what is available.

    Weld MCP server

    Ask your agent.
    It queries PostgreSQL for you.

    Connect Claude, Cursor, ChatGPT or your own agent to Weld over MCP. It reads the Google Cloud Spanner context, finds the tables it needs and runs the query in PostgreSQL.

    Claude CodeOpus 5
    >

    Which Google Cloud Spanner tables do we have in PostgreSQL, and which is the largest?

    Looking up what Weld has synced from Google Cloud Spanner.

    ●weld·search_available_references
    ⎿raw.spanner.*
    tables, columns and freshness
    ●weld·get_reference_schema
    ⎿columns, types and nullability
    ●weld·run_query
    ⎿select count(*) from {{raw.spanner.…}}
    submitted
    ●weld·get_query_status
    ⎿DONE
    ●weld·get_query_result
    ⎿rows returned
    ✓Answered from Google Cloud Spanner data in PostgreSQL
    >Ask about your Google Cloud Spanner data
    Under the hood

    Technical considerations.
    What to expect.

    Incremental syncing
    Weld uses incremental syncing where supported by the Google Cloud Spanner API, loading only new and updated records to minimize data transfer and warehouse costs.
    Schema handling
    Weld automatically manages schema changes. If Google Cloud Spanner adds new fields, they're detected and added to the corresponding PostgreSQL tables.
    Data freshness
    Sync frequency depends on your Weld plan. Most connectors support schedules from every 5 minutes up to daily intervals.
    Security
    All data is encrypted in transit (TLS) and at rest. Weld is SOC 2 Type II compliant and supports IP whitelisting for database connections.
    FAQ

    Common questions.
    About Google Cloud Spanner to PostgreSQL.

    Still have a question?
    Talk to us

    Start syncing Google Cloud Spanner to PostgreSQL.

    Set up your Google Cloud Spanner data pipeline in minutes. No credit card required. Free for 14 days.

    Image not found!
    Source
    WeldWeld
    PostgreSQLWarehouse