INSERT
/UPDATE
operations. Every change to a row must also be reflected in the index, which involves serializing the indexed columns, tokenizing text, updating internal data structures, and potentially triggering compactions.
We’re continuously making improvements to reduce write amplification and optimize background maintenance. See our roadmap for ongoing efforts and
our performance guide for tuning Postgres’ memory and parallelism settings.
COUNT
and “top N” queries.
These queries are accelerated by ParadeDB’s columnar index.
Additionally, ParadeDB provides a set of user-defined functions (UDFs) that allow developers to execute advanced aggregates.
We are currently working on a new custom scan node that can translate native SQL aggregation syntax into ParadeDB’s internal execution model.
Please see the roadmap for more details.
REINDEX
.CREATE TABLE
or CREATE INDEX
.
If ParadeDB is running as a logical replica of a primary Postgres, DDL statements from the primary must be executed manually on the replica.
We recommend version-controlling your schema changes and applying them in a coordinated, repeatable way — either through a migration tool or deployment automation — to keep source and target databases in sync.