summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2011-04-25 16:22:17 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2011-04-25 16:22:17 -0400
commit6ba0d8d5ac47b686ac31a2b390ab6a0f181753d1 (patch)
tree16aba9acd7590b61d2a91904be0515c1f49191e1
parent147d6269f3e2d20e1790520e117e574092719ca3 (diff)
Fix pg_size_pretty() to avoid overflow for inputs close to INT64_MAX.
The expression that tried to round the value to the nearest TB could overflow, leading to bogus output as reported in bug #5993 from Nicola Cossu. This isn't likely to ever happen in the intended usage of the function (if it could, we'd be needing to use a wider datatype instead); but it's not hard to give the expected output, so let's do so.
-rw-r--r--src/backend/utils/adt/dbsize.c8
1 files changed, 7 insertions, 1 deletions
diff --git a/src/backend/utils/adt/dbsize.c b/src/backend/utils/adt/dbsize.c
index 8b5def4d15a..83026b6dde4 100644
--- a/src/backend/utils/adt/dbsize.c
+++ b/src/backend/utils/adt/dbsize.c
@@ -497,9 +497,15 @@ pg_size_pretty(PG_FUNCTION_ARGS)
(size + mult / 2) / mult);
else
{
+ /* Here we have to worry about avoiding overflow */
+ int64 val;
+
mult *= 1024;
+ val = size / mult;
+ if ((size % mult) >= (mult / 2))
+ val++;
snprintf(buf, sizeof(buf), INT64_FORMAT " TB",
- (size + mult / 2) / mult);
+ val);
}
}
}