3 ms·
It seems like having a more robust testing framework might help, akin to what SQLite uses? Obviously easier said than done, but the way he presents things it s
by pstuart 3y ago
It seems like having a more robust testing framework might help, akin to what SQLite uses?
Obviously easier said than done, but the way he presents things it seems kind of like a push and pray environment.
- DowagerDave 3y agoI don't think that's fair. The PostgreSQL codebase includes a lot of stuff that isn't included in SQLite, where it's covered by 3rd party projects - I'd bet their quality is nothing like SQLite or PostgreSQL. Tom Lane was involved in these commits and sounds like some of this got by him. His comments have frequently been described as "complete technical manuals", so I think that speaks to the complexity.
- swader999 3y agoPostgreSQL has different execution paths depending on load, table size, hardware etc which also complicates testing and test setup.
- paulddraper 3y agoPostgreSQL is an order of magnitude more complex and extensible than SQLite. Any comparison is basic at best.
- x0x0 3y agoI suspect it may be closer to 2 orders of magnitude than 1. eg look at the pg docs re: at least 5 different types of indices are implemented https://www.postgresql.org/docs/current/indexes.html https://www.postgresql.org/docs/current/indexes.html Everything is like that. (I'm not bashing sqlite, it's great software, but it has a tiny fraction of the product footprint that pg has.)
- paulddraper 3y ago*6 different index types. And that's just core, not even including built-in extensions like bloom.