wrappers

wrappers : Foreign data wrappers developed by Supabase

Overview

Packages

Source

pig build pkg wrappers;		# build rpm/deb

Install

Make sure PGDG and PIGSTY repo available:

pig repo add pgsql -u   # add both repo and update cache

Install this extension with pig:

pig install wrappers;		# install via package name, for the active PG version

pig install wrappers -v 18;   # install for PG 18
pig install wrappers -v 17;   # install for PG 17
pig install wrappers -v 16;   # install for PG 16
pig install wrappers -v 15;   # install for PG 15
pig install wrappers -v 14;   # install for PG 14

Create this extension with:

CREATE EXTENSION wrappers;

Usage

Sources: official README, official docs, v0.6.1 release

wrappers is both a Rust framework for writing PostgreSQL foreign data wrappers and a packaged collection of Supabase-maintained FDWs. A single extension installs many wrapper implementations, then each foreign server chooses the specific wrapper type it needs.

CREATE EXTENSION wrappers;

Typical Workflow

Create a server for one wrapper, then expose remote data through foreign tables:

CREATE SERVER stripe_server
  FOREIGN DATA WRAPPER stripe_wrapper
  OPTIONS (
    api_key_id 'stripe_api_key',
    api_url 'https://api.stripe.com/v1/'
  );

CREATE FOREIGN TABLE stripe_customers (
  id text,
  email text,
  name text,
  description text,
  created timestamp,
  attrs jsonb
)
  SERVER stripe_server
  OPTIONS (
    object 'customers',
    rowid_column 'id'
  );

What It Covers

Upstream ships wrappers for databases and services such as BigQuery, ClickHouse, DuckDB, DynamoDB, MySQL/Doris, Redis, S3, S3 Vectors, Stripe, Snowflake, Slack, Notion, OpenAPI, Infura, and many others. Read and write support varies by wrapper, but pushdown for WHERE, ORDER BY, and LIMIT is a core framework feature.

Version Notes

The v0.6.1 release keeps the same extension model but expands the catalog and wrapper behavior. Official release notes call out:

• new DynamoDB FDW support
• MySQL/Doris support through mysql_fdw
• schema evolution support for iceberg_fdw
• vault secret lookup by name in _id options
• aggregate pushdown support for COUNT, SUM, AVG, MIN, and MAX, including MySQL FDW support
• parameter-state refresh/rescan fixes and dependency/security updates

Caveats

• Wrapper-specific options, supported objects, and write support differ widely; check the official catalog page for the exact FDW you use.
• The docs warn that logical restores can fail when materialized views depend on foreign tables, so avoid that pattern or rely on physical backups.