All of these #define changes back out VoltDB changes to restore original values from HSQL.
I think HSQL -- possibly including our HSQL backend -- uses the precision values to mean the max decimal digits needed to represent the type's max value.
As far as I can tell, they were never intended to be used as byte counts, which is what VoltDB seems to be trying to turn them into, but NOT for any purpose that I can see.
I don't think that VoltDB uses most of these values.

The one case where I found VoltDB using one of the changed values was DOUBLE_WIDTH that we changed from 128 to be 64.
This change only "seems" to make sense, but it actually had a strange side effect  -- it confused the HSQL code into "promoting" BIG INT multiplications to FLOAT (for LESS actual precision) instead of to DECIMAL for maximum precision.  I don't know why we thought any of these value changes were needed, but I have not been able to find 1 case where they improve system behavior.

So, I thought it would be better to go back to just agreeing with HSQL until we find some specific behavior we don't like -- and then maybe find a safer way of fixing it.