-
- COLLECT_STARTCOLLECTOR (boolean)
-
- Controls whether the postmaster should start the statistics-collection
- subprocess. This is on by default, but may be turned off if you
- know you have no interest in collecting statistics. This option
- can only be set at postmaster start.
-
-
-
-
-
- COLLECT_RESETONPMSTART (boolean)
-
- If on, collected statistics are zeroed out whenever the postmaster
- is restarted. If off, statistics are accumulated across postmaster
- restarts. The default is on. This option
- can only be set at postmaster start.
-
-
-
-
-
- COLLECT_QUERYSTRING (boolean)
- COLLECT_BLOCKLEVEL (boolean)
- COLLECT_TUPLELEVEL (boolean)
-
- These flags determine what information backends send to the statistics
- collector process: current queries, block-level activity statistics,
- or tuple-level activity statistics. All default to off. Enabling
- statistics collection costs a small amount of time per query, but
- is invaluable for debugging and performance tuning.
-
-
-
-
DEBUG_ASSERTIONS (boolean)
+
+ STATS_COMMAND_STRING (boolean)
+ STATS_BLOCK_LEVEL (boolean)
+ STATS_ROW_LEVEL (boolean)
+
+ These flags determine what information backends send to the statistics
+ collector process: current commands, block-level activity statistics,
+ or row-level activity statistics. All default to off. Enabling
+ statistics collection costs a small amount of time per query, but
+ is invaluable for debugging and performance tuning.
+
+
+
+
+
+ STATS_RESET_ON_SERVER_START (boolean)
+
+ If on, collected statistics are zeroed out whenever the server
+ is restarted. If off, statistics are accumulated across server
+ restarts. The default is on. This option
+ can only be set at server start.
+
+
+
+
+
+ STATS_START_COLLECTOR (boolean)
+
+ Controls whether the server should start the statistics-collection
+ subprocess. This is on by default, but may be turned off if you
+ know you have no interest in collecting statistics. This option
+ can only be set at server start.
+
+
+
+
SYSLOG (integer)
-
- TRANSFORM_NULL_EQUALS (boolean)
-
- When turned on, expressions of the form
- expr> = NULL (or
- NULL = expr>) are treated as
- expr> IS NULL, that is, they
- return true if expr> evaluates to the NULL
- value, and false otherwise. The correct behavior of
- expr> = NULL is to always
- return NULL (unknown). Therefore this option defaults to off.
-
-
- However, filtered forms in
Microsoft
- Access generate queries that appear to use
- expr> = NULL to test for
- NULLs, so if you use that interface to access the database you
- might want to turn this option on. Since expressions of the
- form expr> = NULL always
- return NULL (using the correct interpretation) they are not
- very useful and do not appear often in normal applications, so
- this option does little harm in practice. But new users are
- frequently confused about the semantics of expressions
- involving NULL, so we do not turn this option on by default.
-
-
- Note that this option only affects the literal =>
- operator, not other comparison operators or other expressions
- that are computationally equivalent to some expression
- involving the equals operator (such as IN).
- Thus, this option is not a general fix for bad programming.
-
-
- Refer to the User's Guide for related
- information.
-
-
-
-
PORT (integer)
+
+ TRANSFORM_NULL_EQUALS (boolean)
+
+ When turned on, expressions of the form
+ expr> = NULL (or
+ NULL = expr>) are treated as
+ expr> IS NULL, that is, they
+ return true if expr> evaluates to the NULL
+ value, and false otherwise. The correct behavior of
+ expr> = NULL is to always
+ return NULL (unknown). Therefore this option defaults to off.
+
+
+ However, filtered forms in
Microsoft
+ Access generate queries that appear to use
+ expr> = NULL to test for
+ NULLs, so if you use that interface to access the database you
+ might want to turn this option on. Since expressions of the
+ form expr> = NULL always
+ return NULL (using the correct interpretation) they are not
+ very useful and do not appear often in normal applications, so
+ this option does little harm in practice. But new users are
+ frequently confused about the semantics of expressions
+ involving NULL, so we do not turn this option on by default.
+
+
+ Note that this option only affects the literal =>
+ operator, not other comparison operators or other expressions
+ that are computationally equivalent to some expression
+ involving the equals operator (such as IN).
+ Thus, this option is not a general fix for bad programming.
+
+
+ Refer to the User's Guide for related
+ information.
+
+
+
+
UNIX_SOCKET_DIRECTORY (string)
* Support for grand unified configuration scheme, including SET
* command, configuration file, and command line options.
*
- * $Header: /cvsroot/pgsql/src/backend/utils/misc/guc.c,v 1.51 2001/09/21 17:06:12 tgl Exp $
+ * $Header: /cvsroot/pgsql/src/backend/utils/misc/guc.c,v 1.52 2001/09/23 21:52:36 petere Exp $
*
* Copyright 2000 by PostgreSQL Global Development Group
* Written by Peter Eisentraut
.
{"show_btree_build_stats", PGC_SUSET, &Show_btree_build_stats, false, NULL},
#endif
- {"collect_startcollector", PGC_POSTMASTER, &pgstat_collect_startcollector, true, NULL},
- {"collect_resetonpmstart", PGC_POSTMASTER, &pgstat_collect_resetonpmstart, true, NULL},
- {"collect_querystring", PGC_SUSET, &pgstat_collect_querystring, false, NULL},
- {"collect_tuplelevel", PGC_SUSET, &pgstat_collect_tuplelevel, false, NULL},
- {"collect_blocklevel", PGC_SUSET, &pgstat_collect_blocklevel, false, NULL},
+ {"stats_start_collector", PGC_POSTMASTER, &pgstat_collect_startcollector, true, NULL},
+ {"stats_reset_on_server_start", PGC_POSTMASTER, &pgstat_collect_resetonpmstart, true, NULL},
+ {"stats_command_string", PGC_SUSET, &pgstat_collect_querystring, false, NULL},
+ {"stats_row_level", PGC_SUSET, &pgstat_collect_tuplelevel, false, NULL},
+ {"stats_block_level", PGC_SUSET, &pgstat_collect_blocklevel, false, NULL},
{"trace_notify", PGC_USERSET, &Trace_notify, false, NULL},