]> granicus.if.org Git - postgresql/commit
Cap wal_buffers to avoid a server crash when it's set very large.
authorRobert Haas <rhaas@postgresql.org>
Tue, 4 Aug 2015 16:58:54 +0000 (12:58 -0400)
committerRobert Haas <rhaas@postgresql.org>
Tue, 4 Aug 2015 17:05:48 +0000 (13:05 -0400)
commit3a35ca5add65fb58bda52d62695a5b83cd6c0ae7
treea7e39e8760118b3c005c9dac4e05928a58e2c942
parent4424356c033d4f10f7f0d18f2835f219ee09c8c0
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.
src/backend/utils/misc/guc.c