]> 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:52 +0000 (13:05 -0400)
commit11ed4bab50ba6d80cc982cc4ae4675df705eda4b
tree1b89d600e3af9dee9b2ec54a14314449ca7b11ff
parentbd8f768926f7eed520ba30bc135018ec24e0dd91
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