aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistvacuum.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2008-10-05 23:18:37 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2008-10-05 23:18:37 +0000
commit8acfc7594da036f50f8bb79b642fb67bd7a93486 (patch)
tree9f2b35b9ab8a53993c0dcd8ea1a57f575b0c6f31 /src/backend/access/gist/gistvacuum.c
parent1e4b03847c95287a81d531ab2a249ad07081c767 (diff)
downloadpostgresql-8acfc7594da036f50f8bb79b642fb67bd7a93486.tar.gz
postgresql-8acfc7594da036f50f8bb79b642fb67bd7a93486.zip
Tweak the overflow checks in integer division functions to complain if the
machine produces zero (rather than the more usual minimum-possible-integer) for the only possible overflow case. This has been seen to occur for at least some word widths on some hardware, and it's cheap enough to check for everywhere. Per Peter's analysis of buildfarm reports. This could be back-patched, but in the absence of any gripes from the field I doubt it's worth the trouble.
Diffstat (limited to 'src/backend/access/gist/gistvacuum.c')
0 files changed, 0 insertions, 0 deletions