aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRobert Haas <rhaas@postgresql.org>2015-08-04 12:58:54 -0400
committerRobert Haas <rhaas@postgresql.org>2015-08-04 13:05:43 -0400
commitcd52e4a2b945403659219350c4d4c6e6539a1e11 (patch)
tree896cbbfe8a4abee900527fbce76b468a8284b875
parent9d7d0e640c21bfa36e1eeb7e7c9fcdbb2cfb9763 (diff)
downloadpostgresql-cd52e4a2b945403659219350c4d4c6e6539a1e11.tar.gz
postgresql-cd52e4a2b945403659219350c4d4c6e6539a1e11.zip
Cap wal_buffers to avoid a server crash when it's set very large.
It must be possible to multiply wal_buffers by XLOG_BLCKSZ without overflowing int, or calculations in StartupXLOG will go badly wrong and crash the server. Avoid that by imposing a maximum value on wal_buffers. This will be just under 2GB, assuming the usual value for XLOG_BLCKSZ. Josh Berkus, per an analysis by Andrew Gierth.
-rw-r--r--src/backend/utils/misc/guc.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/utils/misc/guc.c b/src/backend/utils/misc/guc.c
index c907ef1e41c..eed5a75845f 100644
--- a/src/backend/utils/misc/guc.c
+++ b/src/backend/utils/misc/guc.c
@@ -2215,7 +2215,7 @@ static struct config_int ConfigureNamesInt[] =
GUC_UNIT_XBLOCKS
},
&XLOGbuffers,
- -1, -1, INT_MAX,
+ -1, -1, (INT_MAX / XLOG_BLCKSZ),
check_wal_buffers, NULL, NULL
},