Commit7e4a629

committed

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.

1 parentab0e426 commit7e4a629Copy full SHA for 7e4a629

File tree

-2

lines changed

-2

lines changed

Lines changed: 2 additions & 2 deletions

Original file line number	Diff line number	Diff line change
`@@ -10,7 +10,7 @@`
`10`	`10`	`* Written by Peter Eisentraut <peter_e@gmx.net>.`
`11`	`11`	`*`
`12`	`12`	`* IDENTIFICATION`
`13`		`- * $Header: /cvsroot/pgsql/src/backend/utils/misc/guc.c,v 1.165 2003/11/06 22:08:15 petere Exp $`
	`13`	`+ * $Header: /cvsroot/pgsql/src/backend/utils/misc/guc.c,v 1.166 2003/11/07 21:27:38 tgl Exp $`
`14`	`14`	`*`
`15`	`15`	`*--------------------------------------------------------------------`
`16`	`16`	`*/`
`@@ -466,7 +466,7 @@ static struct config_bool ConfigureNamesBool[] =`
`466`	`466`	`"zero_damaged_pages to true causes the system to instead report a "`
`467`	`467`	`"warning, zero out the damaged page, and continue processing. This "`
`468`	`468`	`"behavior will destroy data, namely all the rows on the damaged page."),`
`469`		`-GUC_NOT_IN_SAMPLE \|GUC_DISALLOW_IN_FILE`
	`469`	`+GUC_NOT_IN_SAMPLE`
`470`	`470`	`},`
`471`	`471`	`&zero_damaged_pages,`
`472`	`472`	`false,NULL,NULL`

Comments

(0)