3 ms·

I don't know.. but isn't time just the thing we need? The more a library gets used, the more bugs that get discovered. So the bugs get reported, fixed and the

I don't know.. but isn't time just the thing we need? The more a library gets used, the more bugs that get discovered. So the bugs get reported, fixed and the test-set grows, and the software grows more stable? If the api-surface area doesn't change too much, given the right practices, the software should only grow more stable, right? If bugs like these become rarer and rarer over time, then it's fine, no?

bsaul 8y ago
Seems that the bug was introduced in 2016 due to an optimization in ORDERY BY clause. Code that doesn't have to evolve at all for years is very very rare, especially in a product that's used on evolving hardware and software architecture. Responding to parent post, i don't see another solution than theorem provers if we want to pretend that we're doing anything reliable. But it's going to be a long long way...