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, espe

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...