Odyssey vs SPQR
Odyssey
pg-odyssey.techSPQR
docs.pg-sharding.techSide by side
| Figure | Odyssey | SPQR |
|---|---|---|
| Price from | — | Free |
| Free plan | — | Yes |
| Free trial | — | — |
| Open source | — | — |
| macOS | Yes | — |
| Linux | Yes | Yes |
| API | — | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 0 | 1 |
| Spec score · Database Proxy Software | 7.5 (#17) | 7.8 (#9) |
| Deployment | Odyssey can be installed from the PGDG repository, run from a public Docker image, or built locally. | The getting-started guide provides a Docker image and lists router, admin console, and gRPC API ports as 6432, 7432, and 7000. |
| License | The maker's license page permits redistribution and use of source and binary forms, subject to its listed conditions and disclaimer. | The source is distributed under the PostgreSQL Global Development Group License. |
| Support | Users can report issues on the project page or ask usage and development questions in the Telegram community; the project says responses may not be quick. | The project directs users to its Telegram chat for discussion and GitHub Issues for bug reports or feature requests. |
Plans
In their own words
SPQR
SPQR is a self-hosted query router for horizontally scaling PostgreSQL through sharding. It can extract a sharding key from a query and route it to the relevant key range and shard when possible; keys can use one column or several. Queries can also specify a key or shard in a SQL comment. Applications connect using the PostgreSQL protocol, and the router and coordinator provide administrative consoles accessible through psql. SPQR supports one-phase and two-phase commit strategies; two-phase commit provides atomicity across shards and requires max_prepared_transactions greater than zero on each shard. The system can move data between shards to balance workload, and the project describes reducing transferred ranges to limit locking impact. Its documentation includes Docker and configuration-file deployment instructions. SPQR is free and distributed under the PostgreSQL Global Development Group License. The FAQ cautions that it is not suited to complex cross-shard queries, transactions modifying multiple shards or OLAP workloads, and reports a roughly 10–30% performance drop versus vanilla PostgreSQL depending on workload.