Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
Greenplum
Gpdb
提交
c0a92837
G
Gpdb
项目概览
Greenplum
/
Gpdb
通知
7
Star
1
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
DevOps
流水线
流水线任务
计划
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
G
Gpdb
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
DevOps
DevOps
流水线
流水线任务
计划
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
流水线任务
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
提交
c0a92837
编写于
9月 23, 2001
作者:
P
Peter Eisentraut
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Rename collect_* options to more user-friendly names.
上级
9e60c0f6
变更
3
隐藏空白更改
内联
并排
Showing
3 changed file
with
94 addition
and
94 deletion
+94
-94
doc/src/sgml/runtime.sgml
doc/src/sgml/runtime.sgml
+83
-83
src/backend/utils/misc/guc.c
src/backend/utils/misc/guc.c
+6
-6
src/backend/utils/misc/postgresql.conf.sample
src/backend/utils/misc/postgresql.conf.sample
+5
-5
未找到文件。
doc/src/sgml/runtime.sgml
浏览文件 @
c0a92837
<!--
$Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.8
4 2001/09/21 20:31:43 tgl
Exp $
$Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.8
5 2001/09/23 21:52:36 petere
Exp $
-->
<Chapter Id="runtime">
...
...
@@ -780,45 +780,6 @@ env PGOPTIONS='-c geqo=off' psql
<para>
<variablelist>
<varlistentry>
<term><varname>COLLECT_STARTCOLLECTOR</varname> (<type>boolean</type>)</term>
<listitem>
<para>
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.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><varname>COLLECT_RESETONPMSTART</varname> (<type>boolean</type>)</term>
<listitem>
<para>
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.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><varname>COLLECT_QUERYSTRING</varname> (<type>boolean</type>)</term>
<term><varname>COLLECT_BLOCKLEVEL</varname> (<type>boolean</type>)</term>
<term><varname>COLLECT_TUPLELEVEL</varname> (<type>boolean</type>)</term>
<listitem>
<para>
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.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><varname>DEBUG_ASSERTIONS</varname> (<type>boolean</type>)</term>
<listitem>
...
...
@@ -940,6 +901,45 @@ env PGOPTIONS='-c geqo=off' psql
</listitem>
</varlistentry>
<varlistentry>
<term><varname>STATS_COMMAND_STRING</varname> (<type>boolean</type>)</term>
<term><varname>STATS_BLOCK_LEVEL</varname> (<type>boolean</type>)</term>
<term><varname>STATS_ROW_LEVEL</varname> (<type>boolean</type>)</term>
<listitem>
<para>
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.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><varname>STATS_RESET_ON_SERVER_START</varname> (<type>boolean</type>)</term>
<listitem>
<para>
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.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><varname>STATS_START_COLLECTOR</varname> (<type>boolean</type>)</term>
<listitem>
<para>
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.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><varname>SYSLOG</varname> (<type>integer</type>)</term>
<listitem>
...
...
@@ -1268,49 +1268,6 @@ dynamic_library_path = '/usr/local/lib/postgresql:/home/my_project/lib:$libdir'
</listitem>
</varlistentry>
<varlistentry>
<term><varname>TRANSFORM_NULL_EQUALS</varname> (<type>boolean</type>)</term>
<listitem>
<para>
When turned on, expressions of the form
<literal><replaceable>expr</> = NULL</literal> (or
<literal>NULL = <replaceable>expr</></literal>) are treated as
<literal><replaceable>expr</> IS NULL</literal>, that is, they
return true if <replaceable>expr</> evaluates to the NULL
value, and false otherwise. The correct behavior of
<literal><replaceable>expr</> = NULL</literal> is to always
return NULL (unknown). Therefore this option defaults to off.
</para>
<para>
However, filtered forms in <productname>Microsoft
Access</productname> generate queries that appear to use
<literal><replaceable>expr</> = NULL</literal> 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 <literal><replaceable>expr</> = NULL</literal> 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.
</para>
<para>
Note that this option only affects the literal <literal>=</>
operator, not other comparison operators or other expressions
that are computationally equivalent to some expression
involving the equals operator (such as <literal>IN</literal>).
Thus, this option is not a general fix for bad programming.
</para>
<para>
Refer to the <citetitle>User's Guide</citetitle> for related
information.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><varname>PORT</varname> (<type>integer</type>)</term>
<listitem>
...
...
@@ -1408,6 +1365,49 @@ dynamic_library_path = '/usr/local/lib/postgresql:/home/my_project/lib:$libdir'
</listitem>
</varlistentry>
<varlistentry>
<term><varname>TRANSFORM_NULL_EQUALS</varname> (<type>boolean</type>)</term>
<listitem>
<para>
When turned on, expressions of the form
<literal><replaceable>expr</> = NULL</literal> (or
<literal>NULL = <replaceable>expr</></literal>) are treated as
<literal><replaceable>expr</> IS NULL</literal>, that is, they
return true if <replaceable>expr</> evaluates to the NULL
value, and false otherwise. The correct behavior of
<literal><replaceable>expr</> = NULL</literal> is to always
return NULL (unknown). Therefore this option defaults to off.
</para>
<para>
However, filtered forms in <productname>Microsoft
Access</productname> generate queries that appear to use
<literal><replaceable>expr</> = NULL</literal> 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 <literal><replaceable>expr</> = NULL</literal> 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.
</para>
<para>
Note that this option only affects the literal <literal>=</>
operator, not other comparison operators or other expressions
that are computationally equivalent to some expression
involving the equals operator (such as <literal>IN</literal>).
Thus, this option is not a general fix for bad programming.
</para>
<para>
Refer to the <citetitle>User's Guide</citetitle> for related
information.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><varname>UNIX_SOCKET_DIRECTORY</varname> (<type>string</type>)</term>
<listitem>
...
...
src/backend/utils/misc/guc.c
浏览文件 @
c0a92837
...
...
@@ -4,7 +4,7 @@
* 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.5
1 2001/09/21 17:06:12 tgl
Exp $
* $Header: /cvsroot/pgsql/src/backend/utils/misc/guc.c,v 1.5
2 2001/09/23 21:52:36 petere
Exp $
*
* Copyright 2000 by PostgreSQL Global Development Group
* Written by Peter Eisentraut <peter_e@gmx.net>.
...
...
@@ -229,11 +229,11 @@ static struct config_bool
{
"show_btree_build_stats"
,
PGC_SUSET
,
&
Show_btree_build_stats
,
false
,
NULL
},
#endif
{
"
collect_start
collector"
,
PGC_POSTMASTER
,
&
pgstat_collect_startcollector
,
true
,
NULL
},
{
"
collect_resetonpm
start"
,
PGC_POSTMASTER
,
&
pgstat_collect_resetonpmstart
,
true
,
NULL
},
{
"
collect_query
string"
,
PGC_SUSET
,
&
pgstat_collect_querystring
,
false
,
NULL
},
{
"
collect_tuple
level"
,
PGC_SUSET
,
&
pgstat_collect_tuplelevel
,
false
,
NULL
},
{
"
collect_block
level"
,
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
},
...
...
src/backend/utils/misc/postgresql.conf.sample
浏览文件 @
c0a92837
...
...
@@ -150,11 +150,11 @@
#
# Access statistics collection
#
#
collect_start
collector = true
#
collect_resetonpm
start = true
#
collect_query
string = false
#
collect_tuple
level = false
#
collect_block
level = false
#
stats_start_
collector = true
#
stats_reset_on_server_
start = true
#
stats_command_
string = false
#
stats_row_
level = false
#
stats_block_
level = false
#
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录