Skip to main content

ParadeDB Operator

In order for ParadeDB to push down an aggregate, a ParadeDB text search operator must be present in the query.
If your query does not contain a ParadeDB operator, a way to “force” aggregate pushdown is to append the all query to the query’s WHERE clause.

Join Support

Aggregate pushdown works across joins as well as single tables. When every participating table has a ParadeDB index, ParadeDB computes the result directly from the index’s columnar storage, without scanning the underlying table rows. The custom aggregate scan is enabled by default; to turn it off, run SET paradedb.enable_aggregate_custom_scan TO off;. The following join shapes are supported: ParadeDB falls back to native Postgres execution when any of the following are true:
  • One or more tables in the join lacks a ParadeDB index
  • The join has no equality join condition (e.g. CROSS JOIN)
  • Join keys, GROUP BY columns, or aggregate arguments are not indexed columns
  • The query uses window functions (OVER ...), ROLLUP, CUBE, GROUPING SETS, LATERAL, or DISTINCT ON
  • GROUP BY uses a scalar function like date_trunc(...) or lower(...) (JSON sub-field access via ->> is supported)
  • The aggregate argument or result is wrapped in an expression such as COALESCE(SUM(...), 0) or a cast
  • The query uses pdb.agg() (use standard SQL aggregate functions instead)
When a fallback happens, the query still runs correctly through Postgres’ native planner. ParadeDB simply does not accelerate it.