JLockerman

Interestingly the default collation for the database is `en_US.utf8` ``` postgres=# \l List of databases Name | Owner | Encoding | Collate | Ctype | Access privileges -----------+----------+----------+------------+------------+----------------------- postgres |...

It looks this issue is present in the current `timescale/timescaledb:latest-pg12`. I will try to open an error report there. # Error Summary # For stability across machines in multinode, which...

For a short-term fix I'm changing the nightly image to be based on our debian image in PR https://github.com/timescale/timescale-analytics/pull/149; this will make the collation things work, and make the nightly...

@janfockaert switching to a different collation for the hyperloglog should work in the meantime, for instance ```SQL timescale_analytics_experimental.hyperloglog(buckets, data COLLATE "C") ```

note: it probably pays to detect the input collation and if it's deterministic (or default?) just use `C`.

> Thx, the workaround works as expected 👍 The new nightly build is not updated yet, was the build broken maybe? Nope CI builds are currently broken. It works locally...

Nightly builds should be fixed by PR https://github.com/timescale/timescale-analytics/pull/154

Here's my best guess as to what's happening, unfortunately it's not a solution yet, but I figure it'd be a good idea to checkpoint this for everyone to see. ---...

That's an odd one; the C compiler building the shim is building an archive that LLVM can't understand. Is this an M1 mac? They occasionally run into odd issues when...

https://github.com/rust-lang/rust/issues/81790 suggests `arch -arm64` may help