If you’re a non-profit or a non-commercial open source project and are
interested in ParadeDB Enterprise, please contact
sales. We provide complimentary access on a
case-by-case basis.
Feature Comparison
Footnotes
- The ParadeDB index supports Postgres’ multi-version concurrency control (MVCC) rules. The index reflects the current state of the underlying table at all times, changes to the index are atomic, and queries are transactionally consistent with the table.
- The ParadeDB index is built on block storage, Postgres’ native storage API. This means that it leverages the Postgres buffer cache, which minimizes disk I/O.
- Deployment features and limitations are specific to the ParadeDB index. ParadeDB Community can still use standard Postgres replication, crash recovery, and point-in-time recovery for heap tables and other Postgres indexes like B-tree indexes.
- In a primary-replica topology, ParadeDB indexes in ParadeDB Community are only available on the primary because Community does not physically replicate the ParadeDB index.