aboutsummaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2011-10-02 16:50:04 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2011-10-02 16:50:04 -0400
commitd56b3afc0376afe491065d9eca6440b3cc7b1346 (patch)
tree702ba3dcc1dc7f2aeee94635b37a7df5096a7a0c /doc/src
parent5ec6b7f1b87f0fa006b8e08a11cd4e99bcb67358 (diff)
downloadpostgresql-d56b3afc0376afe491065d9eca6440b3cc7b1346.tar.gz
postgresql-d56b3afc0376afe491065d9eca6440b3cc7b1346.zip
Restructure error handling in reading of postgresql.conf.
This patch has two distinct purposes: to report multiple problems in postgresql.conf rather than always bailing out after the first one, and to change the policy for whether changes are applied when there are unrelated errors in postgresql.conf. Formerly the policy was to apply no changes if any errors could be detected, but that had a significant consistency problem, because in some cases specific values might be seen as valid by some processes but invalid by others. This meant that the latter processes would fail to adopt changes in other parameters even though the former processes had done so. The new policy is that during SIGHUP, the file is rejected as a whole if there are any errors in the "name = value" syntax, or if any lines attempt to set nonexistent built-in parameters, or if any lines attempt to set custom parameters whose prefix is not listed in (the new value of) custom_variable_classes. These tests should always give the same results in all processes, and provide what seems a reasonably robust defense against loading values from badly corrupted config files. If these tests pass, all processes will apply all settings that they individually see as good, ignoring (but logging) any they don't. In addition, the postmaster does not abandon reading a configuration file after the first syntax error, but continues to read the file and report syntax errors (up to a maximum of 100 syntax errors per file). The postmaster will still refuse to start up if the configuration file contains any errors at startup time, but these changes allow multiple errors to be detected and reported before quitting. Alexey Klyukin, reviewed by Andy Colson and av (Alexander ?) with some additional hacking by Tom Lane
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/config.sgml4
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index d173af9b9ab..3282ab4f203 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -101,7 +101,9 @@ include 'filename'
value. Alternatively, you can send the signal to a single server
process directly. Some parameters can only be set at server start;
any changes to their entries in the configuration file will be ignored
- until the server is restarted.
+ until the server is restarted. Invalid parameter settings in the
+ configuration file are likewise ignored (but logged) during
+ <systemitem>SIGHUP</> processing.
</para>
<para>