From 73ebf07754cf4deb631d03357cf62d1cf9f46d77 Mon Sep 17 00:00:00 2001 From: Rob A'Court Date: Wed, 18 Dec 2024 13:56:31 +0000 Subject: [PATCH] (website) Fix typo in benchmarks (#2183) --- website/docs/reference/benchmarks.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/reference/benchmarks.md b/website/docs/reference/benchmarks.md index 9d6e7ccc33..01bfb718e5 100644 --- a/website/docs/reference/benchmarks.md +++ b/website/docs/reference/benchmarks.md @@ -187,7 +187,7 @@ is using an optimised where clause, specifically `field = constant`. > When you create a shape, you can specify a where clause that filters the rows that the shape is interested in. > In Electric, we filter the changes we receive from Postgres so that each shape only receives changes that affect the rows it is interested in. > If there are lots of shapes, this could mean we have to evaluate lots of where clauses for each write, however we have optimised this process -> so that we can evalute millions of where clauses at once, providing the where clauses follow various patterns, which we call optimised where clauses. +> so that we can evaluate millions of where clauses at once, providing the where clauses follow various patterns, which we call optimised where clauses. > `field = constant` is one of the patterns we optimise, we can evaluate millions of these where clauses at once by indexing the shapes based on the constant > value for each shape. This index is internal to Electric, and nothing to do with Postgres indexes. It's a hashmap if you're interested. > `field = const AND another_condition` is another pattern we optimise. We aim to optimise a large subset of Postgres where clauses in the future.