From: Robert Haas <rhaas@postgresql.org>
Date: Tue, 27 Jul 2010 16:06:53 +0000 (+0000)
Subject: In postgresql.conf.sample, use on/off rather than true/false.
X-Git-Tag: REL9_1_ALPHA1~175
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=e0226a9bf2dd7e639754d530d21e98c929344f6a;p=postgresql

In postgresql.conf.sample, use on/off rather than true/false.

We used to be consistent about this, but my recent patch to add a
restart_after_crash GUC failed to follow the existing convention.

Report and patch from Fujii Masao.
---

diff --git a/src/backend/utils/misc/postgresql.conf.sample b/src/backend/utils/misc/postgresql.conf.sample
index d3c07bd502..d31f1a1dbf 100644
--- a/src/backend/utils/misc/postgresql.conf.sample
+++ b/src/backend/utils/misc/postgresql.conf.sample
@@ -524,8 +524,8 @@
 # ERROR HANDLING
 #------------------------------------------------------------------------------
 
-#exit_on_error = false				# terminate session on any error?
-#restart_after_crash = true			# reinitialize after backend crash?
+#exit_on_error = off				# terminate session on any error?
+#restart_after_crash = on			# reinitialize after backend crash?
 
 
 #------------------------------------------------------------------------------