BUG #7799: Several configuration options in guc.c miss descriptions

Started by Tianyin Xuover 13 years ago2 messagesbugs
Jump to latest
#1Tianyin Xu
tixu@cs.ucsd.edu

The following bug has been logged on the website:

Bug reference: 7799
Logged by: Tianyin Xu
Email address: tixu@cs.ucsd.edu
PostgreSQL version: 9.2.2
Operating system: any
Description:

Hi, I just noticed that several developer options do not have descriptions
(in src/backend/utils/misc/guc.c) with the text "No description available."

I wrote the desc. according to the online doc, see below.

HTH

--- src/backend/utils/misc/guc.c
+++ src/backend/utils/misc/guc.c.
@@ -988,7 +988,7 @@ static struct config_bool ConfigureNamesBool[] =
 #ifdef BTREE_BUILD_STATS
 	{
 		{"log_btree_build_stats", PGC_SUSET, DEVELOPER_OPTIONS,
-			gettext_noop("No description available."),
+			gettext_noop("Logs system resource usage statistics (memory and CPU) on
various B-tree operations."),
 			NULL,
 			GUC_NOT_IN_SAMPLE
 		},
@@ -1062,7 +1062,7 @@ static struct config_bool ConfigureNamesBool[] =
 #ifdef LOCK_DEBUG
 	{
 		{"trace_locks", PGC_SUSET, DEVELOPER_OPTIONS,
-			gettext_noop("No description available."),
+			gettext_noop("Emits information about lock usage."),
 			NULL,
 			GUC_NOT_IN_SAMPLE
 		},
@@ -1072,7 +1072,7 @@ static struct config_bool ConfigureNamesBool[] =
 	},
 	{
 		{"trace_userlocks", PGC_SUSET, DEVELOPER_OPTIONS,
-			gettext_noop("No description available."),
+			gettext_noop("Emits information about user lock usage."),
 			NULL,
 			GUC_NOT_IN_SAMPLE
 		},
@@ -1082,7 +1082,7 @@ static struct config_bool ConfigureNamesBool[] =
 	},
 	{
 		{"trace_lwlocks", PGC_SUSET, DEVELOPER_OPTIONS,
-			gettext_noop("No description available."),
+			gettext_noop("Emits information about lightweight lock usage."),
 			NULL,
 			GUC_NOT_IN_SAMPLE
 		},
@@ -1092,7 +1092,7 @@ static struct config_bool ConfigureNamesBool[] =
 	},
 	{
 		{"debug_deadlocks", PGC_SUSET, DEVELOPER_OPTIONS,
-			gettext_noop("No description available."),
+			gettext_noop("Dumps information about all current locks when a deadlock
timeout occurs."),
 			NULL,
 			GUC_NOT_IN_SAMPLE
 		},
@@ -1828,8 +1828,8 @@ static struct config_int ConfigureNamesInt[] =
 #ifdef LOCK_DEBUG
 	{
 		{"trace_lock_oidmin", PGC_SUSET, DEVELOPER_OPTIONS,
-			gettext_noop("No description available."),
-			NULL,
+			gettext_noop("Sets the minimum OID of tables for tracking locks."),
+			gettext_noop("Is used to avoid output on system tables."),
 			GUC_NOT_IN_SAMPLE
 		},
 		&Trace_lock_oidmin,
@@ -1838,7 +1838,7 @@ static struct config_int ConfigureNamesInt[] =
 	},
 	{
 		{"trace_lock_table", PGC_SUSET, DEVELOPER_OPTIONS,
-			gettext_noop("No description available."),
+			gettext_noop("Sets the OID of the table with unconditionally lock
tracing."),
 			NULL,
 			GUC_NOT_IN_SAMPLE
 		},

--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

#2Bruce Momjian
bruce@momjian.us
In reply to: Tianyin Xu (#1)
Re: BUG #7799: Several configuration options in guc.c miss descriptions

Thanks. This will appear in PG 9.4.

---------------------------------------------------------------------------

On Tue, Jan 8, 2013 at 07:24:57AM +0000, tixu@cs.ucsd.edu wrote:

The following bug has been logged on the website:

Bug reference: 7799
Logged by: Tianyin Xu
Email address: tixu@cs.ucsd.edu
PostgreSQL version: 9.2.2
Operating system: any
Description:

Hi, I just noticed that several developer options do not have descriptions
(in src/backend/utils/misc/guc.c) with the text "No description available."

I wrote the desc. according to the online doc, see below.

HTH

--- src/backend/utils/misc/guc.c
+++ src/backend/utils/misc/guc.c.
@@ -988,7 +988,7 @@ static struct config_bool ConfigureNamesBool[] =
#ifdef BTREE_BUILD_STATS
{
{"log_btree_build_stats", PGC_SUSET, DEVELOPER_OPTIONS,
-			gettext_noop("No description available."),
+			gettext_noop("Logs system resource usage statistics (memory and CPU) on
various B-tree operations."),
NULL,
GUC_NOT_IN_SAMPLE
},
@@ -1062,7 +1062,7 @@ static struct config_bool ConfigureNamesBool[] =
#ifdef LOCK_DEBUG
{
{"trace_locks", PGC_SUSET, DEVELOPER_OPTIONS,
-			gettext_noop("No description available."),
+			gettext_noop("Emits information about lock usage."),
NULL,
GUC_NOT_IN_SAMPLE
},
@@ -1072,7 +1072,7 @@ static struct config_bool ConfigureNamesBool[] =
},
{
{"trace_userlocks", PGC_SUSET, DEVELOPER_OPTIONS,
-			gettext_noop("No description available."),
+			gettext_noop("Emits information about user lock usage."),
NULL,
GUC_NOT_IN_SAMPLE
},
@@ -1082,7 +1082,7 @@ static struct config_bool ConfigureNamesBool[] =
},
{
{"trace_lwlocks", PGC_SUSET, DEVELOPER_OPTIONS,
-			gettext_noop("No description available."),
+			gettext_noop("Emits information about lightweight lock usage."),
NULL,
GUC_NOT_IN_SAMPLE
},
@@ -1092,7 +1092,7 @@ static struct config_bool ConfigureNamesBool[] =
},
{
{"debug_deadlocks", PGC_SUSET, DEVELOPER_OPTIONS,
-			gettext_noop("No description available."),
+			gettext_noop("Dumps information about all current locks when a deadlock
timeout occurs."),
NULL,
GUC_NOT_IN_SAMPLE
},
@@ -1828,8 +1828,8 @@ static struct config_int ConfigureNamesInt[] =
#ifdef LOCK_DEBUG
{
{"trace_lock_oidmin", PGC_SUSET, DEVELOPER_OPTIONS,
-			gettext_noop("No description available."),
-			NULL,
+			gettext_noop("Sets the minimum OID of tables for tracking locks."),
+			gettext_noop("Is used to avoid output on system tables."),
GUC_NOT_IN_SAMPLE
},
&Trace_lock_oidmin,
@@ -1838,7 +1838,7 @@ static struct config_int ConfigureNamesInt[] =
},
{
{"trace_lock_table", PGC_SUSET, DEVELOPER_OPTIONS,
-			gettext_noop("No description available."),
+			gettext_noop("Sets the OID of the table with unconditionally lock
tracing."),
NULL,
GUC_NOT_IN_SAMPLE
},

--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs