4 ms·
I was curious what the claim "10-100x uplift in terms of speed compared to Postgres on things like regexp_matches()" was about, so I checked, and DuckDB's reg
by JoelJacobson 4mo ago
I was curious what the claim
"10-100x uplift in terms of speed compared to Postgres on things like regexp_matches()"
was about, so I checked, and DuckDB's regexp_matches() is not the same as PostgreSQL's regexp_matches(). DuckDB's version "Returns true if string contains the regexp pattern, false otherwise." [1] while PostgreSQL's "returns a set of text arrays of matching substring(s)" [2].
I think the closest think in PostgreSQL to DuckDB's regexp_matches() is `string ~ pattern` or `regexp_like(string, pattern)`.
[1] https://duckdb.org/docs/lts/sql/functions/regular_expressions https://duckdb.org/docs/lts/sql/functions/regular_expression...
[2] https://www.postgresql.org/docs/current/functions-matching.html https://www.postgresql.org/docs/current/functions-matching.h...