- Home
- Data Federation Software
- PGSpider
PGSpider
What it is
PGSpider is a SQL cluster engine for querying distributed data through Foreign Data Wrappers. It can bring similarly structured tables from multiple sources together as a Multi-Tenant virtual table, which clients can query with one SQL statement. Queries and result retrieval run in parallel across child nodes. PGSpider can also send WHERE conditions and aggregation work to those nodes; supported Multi-Tenant aggregates include AVG, STDDEV, and VARIANCE. Multi-Tenant tables allow INSERT, UPDATE, DELETE, and batch INSERT through a batch_size option. The README demonstrates PostgreSQL and SQLite and lists PostgreSQL, MySQL, Oracle, GridDB, PGSpider, InfluxDB v2.0, and Amazon S3 Parquet storage for migration. It uses PostgreSQL-like operation and documents client use with libpq and psql. PGSpider is free and open source, for self-hosted Linux deployment; documented installation involves building from source. Modification limits include unsupported RETURNING, WITH CHECK OPTION, and ON CONFLICT, as well as foreign-partition COPY and modification. The README recommends auto-commit for modifications. Its tree-structure feature is in beta and described as not tested enough.
For and against
For
- Combines similar tables into one virtual table.
- Runs queries and fetches results in parallel.
- Pushes WHERE clauses and supported aggregates to child nodes.
- Supports INSERT, UPDATE, DELETE, and batch INSERT.
- Free, open-source license permits use and modification.
Against
- Requires self-hosted Linux deployment.
- Several modification patterns are unsupported.
- Modifications are recommended in auto-commit mode.
- Tree-structure feature is in beta.
The verdict
PGSpider brings distributed data sources into a SQL querying workflow and supports several data modification operations. Review its modification restrictions and beta tree feature before choosing it.
Who it suits
PGSpider suits teams that want to query data across multiple sources through SQL in a self-hosted Linux setup. Its documented client compatibility may suit users of libpq or psql.
Plans and prices
PGSpider
Use, copy, modify, and distribute under the included license
Read 4 Oct 2026 · github.com
On the record
- Client compatibility
- PGSpider uses PostgreSQL-like operation and documents use with client applications such as libpq and psql.github.com · read 4 Oct 2026
- Cloud transfer
- Data Compression Transfer sends compressed data through a Cloud Function and requires a pgspider_fdw relay server with endpoint and relay options.github.com · read 4 Oct 2026
- Data modification
- Multi-Tenant tables support INSERT, UPDATE, and DELETE, as well as bulk INSERT using a batch_size option.github.com · read 4 Oct 2026
- Data sources
- The README demonstrates PostgreSQL and SQLite and lists PostgreSQL, MySQL, Oracle, GridDB, PGSpider, InfluxDB v2.0, and Amazon S3 Parquet storage for migration.github.com · read 4 Oct 2026
- Deployment
- The README documents building from source and installing to /usr/local/pgspider.github.com · read 4 Oct 2026
- License
- The included license permits use, copying, modification, and distribution without a fee, and disclaims warranties and an obligation to provide support or updates.github.com · read 4 Oct 2026
- Modification limitation
- RETURNING, WITH CHECK OPTION, and ON CONFLICT are unsupported with modification, and foreign-partition COPY and modification are unsupported.github.com · read 4 Oct 2026
- Parallel queries
- PGSpider runs queries and fetches results from child nodes in parallel.github.com · read 4 Oct 2026
- Purpose
- PGSpider is a SQL cluster engine for distributed big data that accesses data sources through Foreign Data Wrappers.github.com · read 4 Oct 2026
- Pushdown
- It pushes WHERE clauses and aggregation functions down to child nodes, and supports AVG, STDDEV, and VARIANCE on Multi-Tenant tables.github.com · read 4 Oct 2026
- Transaction limitation
- The README recommends running modifications in auto-commit mode because modified data may not be readable within a transaction and non-auto-commit changes may be inconsistent.github.com · read 4 Oct 2026
- Tree feature status
- The README says the tree-structure feature is not tested enough and is in beta.github.com · read 4 Oct 2026
- Virtual tables
- It can present similarly structured tables from multiple data sources as one Multi-Tenant virtual table queried with a single SQL statement.github.com · read 4 Oct 2026
