database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-05-18 17:41:14 +03:00
Code

zero_damaged_pages must absolutely NOT be marked GUC_DISALLOW_IN_FILE,

Browse Source 
else it cannot be used to handle failures detected during WAL replay.
Fortunately this flag isn't actually enforced yet, but get it right.
This commit is contained in:
Tom Lane 2003-11-07 21:27:50 +00:00
parent fece53069b
commit 8762e10174
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
src/backend/utils/misc/guc.c
View File

@ -10,7 +10,7 @@
* Written by Peter Eisentraut <peter_e@gmx.net>.
*
* IDENTIFICATION
* $Header: /cvsroot/pgsql/src/backend/utils/misc/guc.c,v 1.164 2003/10/18 22:59:09 petere Exp $
* $Header: /cvsroot/pgsql/src/backend/utils/misc/guc.c,v 1.164.2.1 2003/11/07 21:27:50 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