Cap wal_buffers to avoid a server crash when it's set very large.
authorRobert Haas <[email protected]>
Tue, 4 Aug 2015 16:58:54 +0000 (12:58 -0400)
committerRobert Haas <[email protected]>
Tue, 4 Aug 2015 17:05:58 +0000 (13:05 -0400)
commit5ef8e1114774ea65eb03f48846e1d708ca8da4be
tree2e3c5513361cc9660b63cfa11a8ceb9c3132c134
parent121869fe41a73ae4381b4d1342b0f9f114866326
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