From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Fri, 7 Nov 2003 21:27:38 +0000 (+0000)
Subject: zero_damaged_pages must absolutely NOT be marked GUC_DISALLOW_IN_FILE,
X-Git-Tag: REL8_0_0BETA1~1743
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=7e4a6294929cc0c9bb17441e639c013b679a127b;p=postgresql

zero_damaged_pages must absolutely NOT be marked GUC_DISALLOW_IN_FILE,
else it cannot be used to handle failures detected during WAL replay.
Fortunately this flag isn't actually enforced yet, but get it right.
---

diff --git a/src/backend/utils/misc/guc.c b/src/backend/utils/misc/guc.c
index fd9def3e6c..44e492b6a9 100644
--- a/src/backend/utils/misc/guc.c
+++ b/src/backend/utils/misc/guc.c
@@ -10,7 +10,7 @@
  * Written by Peter Eisentraut <peter_e@gmx.net>.
  *
  * IDENTIFICATION
- *	  $Header: /cvsroot/pgsql/src/backend/utils/misc/guc.c,v 1.165 2003/11/06 22:08:15 petere Exp $
+ *	  $Header: /cvsroot/pgsql/src/backend/utils/misc/guc.c,v 1.166 2003/11/07 21:27:38 tgl Exp $
  *
  *--------------------------------------------------------------------
  */
@@ -466,7 +466,7 @@ static struct config_bool ConfigureNamesBool[] =
 						 "zero_damaged_pages to true causes the system to instead report a "
 						 "warning, zero out the damaged page, and continue processing. This "
 						 "behavior will destroy data, namely all the rows on the damaged page."),
-			GUC_NOT_IN_SAMPLE | GUC_DISALLOW_IN_FILE
+			GUC_NOT_IN_SAMPLE
 		},
 		&zero_damaged_pages,
 		false, NULL, NULL