> To me this is a contradiction, whether you consider waiting for a segfault or consider adding an Assert. > For the user it is better to have a log, where he can quickly find the problem, rather than having to investigate on his own.
That's the point. User's shouldn't encounter this.
It shouldn't.
Thus there is no reason to break branch prediction for everyone here.
For now there is no consensus that there will not be a segfault.
If a segfault will never occur, ok.
IMO, this is not a query-dependent issue. But the table in question is never corrupted or invalid.
