"Magnus Hagander" <[EMAIL PROTECTED]> writes:
> What we get is Integer Overflow, on the instruction "idiv esi" in
> postgres!int4div+0x1f. (Per windows debugger.) Same does not happen on Linux.
> Tom - hints? ;-) Any idea why this happens on win32 but not linux?
Perhaps there's some process-wide setting that enables or disables that?
It seems fairly inconsistent to have a machine trap on divide overflow
when it doesn't on any other integer overflow, so I'd rather turn it off
than work around it.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings
