On 2019-03-01 11:04:04 -0700, David G. Johnston wrote: > Changing the behavior is not going to happen for any existing data types.
For the overflow case that really sucks, because we're leaving a very significant amount of performance on the table because we recheck for overflow in every op. The actual float operation is basically free, but the overflow check and the calling convention is not. JIT can get of the latter, but not the former. Which is why we spend like 30% in one of the TPCH queries doing overflow checks... I still kinda wonder whether we can make trapping operations work, but it's not trivial.
