Gurjeet Singh wrote: > 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.
Actually, no one else has been confused by this wording before, and I can't think of better wording that doesn't sound redundant. -- Bruce Momjian <[EMAIL PROTECTED]> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
