Tom Lane wrote:

"Zeugswetter Andreas SB SD" <[EMAIL PROTECTED]> writes:

! } while (!(z > 0 && z < MAX_RANDOM_VALUE));

! } while (z == 0 || z == MAX_RANDOM_VALUE);

This seems fairly ugly, since it eliminates the original coding's
positive guarantee that the final result is in 0 < x < 1.  Does your
compiler manage not to choke if we add a cast instead?

} while (!(z > 0 && z < (long) MAX_RANDOM_VALUE));

Or put an "L" suffix on the value in pg_config_manual.h, so it gets picked up everywhere?



---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match

Reply via email to