Hacker News new | ask | show | jobs
by 1egg0myegg0 1126 days ago
Sorry to hear that!

(I work on docs for the DuckDB Foundation)

Starting in this release, the DuckDB team invested significantly in adding memory safety throughout catalog operations. There is more on the roadmap, but I would expect this release and all following to have improved stability!

That said, at my primary company, we have used it in production for years now with great success!
1 comments
TACIXAT 1126 days ago
Yea, legit a cool project and if it wasn't on customer machines and being passed user-defined SQL it would have just been worked around.
link
chrisjc 1126 days ago
Would you mind explaining your issues in a little more detail?

> being passed user-defined SQL

What does this mean exactly? Customers were writing their own SQL on their own machines? Maybe expensive operations such as:

`SELECT ROW_NUMBER() OVER (PARTITION BY THING ORDER BY TS), * FROM EVENTS`

And since it was on a customer's machine, it became a problem you had no control over?

link