pgsql: Cap wal_buffers to avoid a server crash when it's set very large
pgsql: Cap wal_buffers to avoid a server crash when it's set very large
От:
Robert Haas <rhaas@postgresql.org>
Дата:
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. Branch ------ REL9_2_STABLE Details ------- http://git.postgresql.org/pg/commitdiff/5ef8e1114774ea65eb03f48846e1d708ca8da4be Modified Files -------------- src/backend/utils/misc/guc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)