Skip site navigation (1) Skip section navigation (2)

wal_buffers = -1 and SIGHUP

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@[] (view raw, whole thread or download thread mbox)
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.



pgsql-hackers by date

Next:From: Kevin GrittnerDate: 2011-03-31 13:31:40
Subject: Re: SSI bug?
Previous:From: Bernd HelmleDate: 2011-03-31 12:35:43
Subject: Re: BUG #5856: pg_attribute.attinhcount is not correct.

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group