]> 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:12:03 +0000 (13:12 -0400)
commitb09446ed7eecc7cee6f7cc1dcc954c75c6c7570b
tree7dacd508aba1a7f3f671e17da31e5e0bee51b228
parent8b53c087d2685e187b8a8e2ea8b924d597396f2b
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