BigQuery Wrapper

BigQuery is Google Cloud's autonomous data and AI platform: a serverless data warehouse built for petabyte-scale analytics, with built-in ML, multimodal data support, and Gemini-powered AI features. It's where teams run large analytical workloads that don't belong in an operational database.

The BigQuery Wrapper brings that warehouse into your Postgres database. Query BigQuery tables and views directly with SQL, write data back from Postgres, and join warehouse results against your live application data. No ETL pipelines, no data movement, no scheduled syncs.

Supports both read and write operations, and works with Supabase Vault for secure service account credential management.

Supported Operations

Operation	Supported
Select	✅
Insert	✅
Update	✅
Delete	✅

Supported Data Types

Postgres Type	BigQuery Type
boolean	BOOL
bigint	INT64
double precision	FLOAT64
numeric	NUMERIC
text	STRING
varchar	STRING
date	DATE
timestamp	DATETIME
timestamp	TIMESTAMP

Preparation

Before you get started, make sure the wrappers extension is installed on your database:

and then create the foreign data wrapper:

Secure your credentials (optional)

By default, Postgres stores FDW credentials inside pg_catalog.pg_foreign_server in plain text. Anyone with access to this table will be able to view these credentials. Wrappers is designed to work with Vault, which provides an additional level of security for storing credentials. We recommend using Vault to store your credentials.

Connecting to BigQuery

We need to provide Postgres with the credentials to connect to BigQuery, and any additional options. We can do this using the create server command:

With Vault:

Without Vault:

Resources

• Supabase docs: Connecting to BigQuery
• Enable in Supabase dashboard
• supabase/wrappers on GitHub
• BigQuery product page
• Official supabase/wrappers documentation