aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/formatting.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2021-04-11 17:02:04 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2021-04-11 17:02:04 -0400
commit6277435a8a89c59f716c111200c072d1454b8ff2 (patch)
tree06775adadf874620b832885b48c1fe09f7cacb24 /src/backend/utils/adt/formatting.c
parentd7cff12c4c035b7cf12bb8454824f48f13018730 (diff)
downloadpostgresql-6277435a8a89c59f716c111200c072d1454b8ff2.tar.gz
postgresql-6277435a8a89c59f716c111200c072d1454b8ff2.zip
Silence some Coverity warnings and improve code consistency.
Coverity complained about possible overflow in expressions like intresult = tm->tm_sec * 1000000 + fsec; on the grounds that the multiplication would happen in 32-bit arithmetic before widening to the int64 result. I think these are all false positives because of the limited possible range of tm_sec; but nonetheless it seems silly to spell it like that when nearby lines have the identical computation written with a 64-bit constant. ... or more accurately, with an LL constant, which is not project style. Make all of these use INT64CONST(), as we do elsewhere. This is all new code from a2da77cdb, so no need for back-patch.
Diffstat (limited to 'src/backend/utils/adt/formatting.c')
0 files changed, 0 insertions, 0 deletions