wal_buffers = -1 and SIGHUP

Lists: pgsql-hackers
From: Bernd Helmle <mailings(at)oopsware(dot)de>
To: pgsql-hackers(at)postgresql(dot)org
Subject: wal_buffers = -1 and SIGHUP
Date: 2011-03-31 12:38:00
Message-ID: 03B05B92CB72954D84334E47@[172.26.14.62]
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

This might be nitpicking (or i'm currently missing something), but i recognized
that setting wal_buffers = -1 always triggers the following on reload, even if
nothing to wal_buffers had changed:

$ pg_ctl reload
LOG: received SIGHUP, reloading configuration files
LOG: parameter "wal_buffers" cannot be changed without restarting the server

This only happens when you have wal_buffers set to -1.

--
Thanks

Bernd