From a385186ff737a935631efd9ff4294588988e67fb Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Thu, 3 Apr 2003 23:32:47 +0000 Subject: Remove zero_damaged_pages from postgresql.conf.sample; the only way to find out about it is to read the documentation that tells you how dangerous it is. Add default_transaction_read_only to documentation; seems to have been overlooked in patch that added read-only transactions. Clean up check_guc comparison script, which has been suffering bit rot. --- src/backend/utils/misc/postgresql.conf.sample | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/backend/utils/misc/postgresql.conf.sample') diff --git a/src/backend/utils/misc/postgresql.conf.sample b/src/backend/utils/misc/postgresql.conf.sample index 7039a7572a3..f32aa3ff4cb 100644 --- a/src/backend/utils/misc/postgresql.conf.sample +++ b/src/backend/utils/misc/postgresql.conf.sample @@ -205,6 +205,7 @@ #authentication_timeout = 60 # 1-600, in seconds #deadlock_timeout = 1000 # in milliseconds #default_transaction_isolation = 'read committed' +#default_transaction_read_only = false #extra_float_digits = 0 # min -15, max 2 #max_expr_depth = 10000 # min 10 #max_files_per_process = 1000 # min 25 @@ -213,6 +214,5 @@ #sql_inheritance = true #transform_null_equals = false #statement_timeout = 0 # 0 is disabled, in milliseconds -#zero_damaged_pages = false # set this true only for disaster recovery #db_user_namespace = false #preload_libraries = '' -- cgit v1.2.3