]> 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:06:03 +0000 (13:06 -0400)
commit4e51ea8fd26f743d92cd35905eac334aafe2b1cc
tree0a57cbc159bf9e32ac6b40d0a268a2ccab791ce8
parent1e1bb203bcfdb90ef81e97169812a5f5f942b124
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