Confusing message in log file

------=_Part_4257_30163614.1210826623742
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi All,

    I changed the postgresql.conf file (of an 8.2.4 server), and issued
relaod using pg_reload_config(). Following are the messages I see in the
log
files:

May 14 21:38:40 sfphotodb001 postgres[29658]: [19-1] 2008-05-14 21:38:40
PDTLOG:  received SIGHUP, reloading configuration files
May 14 21:38:40 sfphotodb001 postgres[29658]: [20-1] 2008-05-14 21:38:40
PDTLOG:  parameter "shared_buffers" cannot be changed after server start;
configuration file change ignored
May 14 21:39:03 sfphotodb001 postgres[22928]: [21-1] 2008-05-14 21:39:03
PDTLOG:  archived transaction log file "0000000100000E23000000C8"


    What's confusing about this is that the second message says
'configuration file change ignored', so I expect the changed (newly
enabled)
archive_command to not take effect. But in fact, it does take effect.

    The message probably should be rephrased to say that this setting
(shared_buffers) will not be changed.

Best regards,

-- 
gurjeet[.singh]@[EMAIL PROTECTED]
 gmail | hotmail | indiatimes | yahoo }.com

EnterpriseDB http://www.enterprisedb.com

Mail sent from my BlackLaptop device

------=_Part_4257_30163614.1210826623742
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi All,<br><br>&nbsp;&nbsp;&nbsp; I changed the postgresql.conf file (of
an 8.2.4 server), and issued relaod using pg_reload_config(). Following
are the messages I see in the log files:<br><br>May 14 21:38:40
sfphotodb001 postgres[29658]: [19-1] 2008-05-14 21:38:40 PDTLOG:&nbsp;
received SIGHUP, reloading configuration files<br>
May 14 21:38:40 sfphotodb001 postgres[29658]: [20-1] 2008-05-14 21:38:40
PDTLOG:&nbsp; parameter &quot;shared_buffers&quot; cannot be changed after
server start; configuration file change ignored<br>May 14 21:39:03
sfphotodb001 postgres[22928]: [21-1] 2008-05-14 21:39:03 PDTLOG:&nbsp;
archived transaction log file &quot;0000000100000E23000000C8&quot;<br>
<br><br>&nbsp;&nbsp;&nbsp; What&#39;s confusing about this is that the
second message says &#39;configuration file change ignored&#39;, so I
expect the changed (newly enabled) archive_command to not take effect. But
in fact, it does take effect.<br>
<br>&nbsp;&nbsp;&nbsp; The message probably should be rephrased to say
that this setting (shared_buffers) will not be changed.<br><br>Best
regards,<br clear="all"><br>--
<br>gurjeet[.singh]@[EMAIL PROTECTED]
>singh.gurjeet@[EMAIL PROTECTED]
 gmail | hotmail |
indiatimes | yahoo }.com<br>
<br>EnterpriseDB <a
href="http://www.enterprisedb.com">http://www.enterprisedb.com</a><br><br>Mail
sent from my BlackLaptop device

------=_Part_4257_30163614.1210826623742--