News for hackers. Stuff that matters.

A comment on Making Postgres 300x faster for analytics: batching, operator fusion, and SIMD.

Re:Making Postgres 300x faster for analytics: batching, oper... by mdkdog on Saturday August 08, 2026 @05:27AM (#49220159)
wanted to test this but no joy.

"ERROR: convert_string_datum (selfuncs.c): pg_strxfrm leg; C-collation lane only" "thread 'pg:backend:1572' (11650) panicked at crates/backend/optimizer/plan/planner/src/selfuncs.rs:966:9:"

i would say is not ready yet.

[ Parent | on HN ]
Re:Making Postgres 300x faster for analytics: batching, oper... by malisper on Saturday August 08, 2026 @08:01AM (#49221003)
Can you file an issue? We know there are bugs and the work we're doing with formal verification and fuzz testing is to go through all the code and make sure all of it behaves identically to Postgres
[ Parent | on HN ]
Re:Making Postgres 300x faster for analytics: batching, oper... by malisper on Saturday August 08, 2026 @09:36PM (#49227575)
We've fixed the issue on our development branch. We've only been working with the default collation so when you try a different one it causes an issue
[ Parent | on HN ]