Understood: SQLite is to Postgres as DuckDB is to ClickHouse.
I don’t see the analogy, if you’re using it to excuse crashing on small data sets and indexes.
SQLite isn’t small and crashy, it’s small and reliable.
There’s something fundamentally wrong with the codebase/architecture if there’s so many memory problems.
And the absolute baseline requirement for a production database is no crashes.
I don’t see the analogy, if you’re using it to excuse crashing on small data sets and indexes.
SQLite isn’t small and crashy, it’s small and reliable.
There’s something fundamentally wrong with the codebase/architecture if there’s so many memory problems.
And the absolute baseline requirement for a production database is no crashes.