|
1 | 1 | <!--
|
2 |
| -$Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.81 2001/09/20 14:20:27 petere Exp $ |
| 2 | +$Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.82 2001/09/21 03:32:35 tgl Exp $ |
3 | 3 | -->
|
4 | 4 |
|
5 | 5 | <Chapter Id="runtime">
|
@@ -780,6 +780,45 @@ env PGOPTIONS='-c geqo=off' psql
|
780 | 780 |
|
781 | 781 | <para>
|
782 | 782 | <variablelist>
|
| 783 | + <varlistentry> |
| 784 | + <term><varname>COLLECT_STARTCOLLECTOR</varname> (<type>boolean</type>)</term> |
| 785 | + <listitem> |
| 786 | + <para> |
| 787 | + Controls whether the postmaster should start the statistics-collection |
| 788 | + subprocess. This is on by default, but may be turned off if you |
| 789 | + know you have no interest in collecting statistics. This option |
| 790 | + can only be set at postmaster start. |
| 791 | + </para> |
| 792 | + </listitem> |
| 793 | + </varlistentry> |
| 794 | + |
| 795 | + <varlistentry> |
| 796 | + <term><varname>COLLECT_RESETONPMSTART</varname> (<type>boolean</type>)</term> |
| 797 | + <listitem> |
| 798 | + <para> |
| 799 | + If on, collected statistics are zeroed out whenever the postmaster |
| 800 | + is restarted. If off, statistics are accumulated across postmaster |
| 801 | + restarts. The default is on. This option |
| 802 | + can only be set at postmaster start. |
| 803 | + </para> |
| 804 | + </listitem> |
| 805 | + </varlistentry> |
| 806 | + |
| 807 | + <varlistentry> |
| 808 | + <term><varname>COLLECT_QUERYSTRING</varname> (<type>boolean</type>)</term> |
| 809 | + <term><varname>COLLECT_BLOCKLEVEL</varname> (<type>boolean</type>)</term> |
| 810 | + <term><varname>COLLECT_TUPLELEVEL</varname> (<type>boolean</type>)</term> |
| 811 | + <listitem> |
| 812 | + <para> |
| 813 | + These flags determine what information backends send to the statistics |
| 814 | + collector process: current queries, block-level activity statistics, |
| 815 | + or tuple-level activity statistics. All default to off. Enabling |
| 816 | + statistics collection costs a small amount of time per query, but |
| 817 | + is invaluable for debugging and performance tuning. |
| 818 | + </para> |
| 819 | + </listitem> |
| 820 | + </varlistentry> |
| 821 | + |
783 | 822 | <varlistentry>
|
784 | 823 | <term><varname>DEBUG_ASSERTIONS</varname> (<type>boolean</type>)</term>
|
785 | 824 | <listitem>
|
@@ -1013,7 +1052,7 @@ env PGOPTIONS='-c geqo=off' psql
|
1013 | 1052 | <primary>transaction isolation level</primary>
|
1014 | 1053 | </indexterm>
|
1015 | 1054 |
|
1016 |
| - <term><varname>DEFAUL_TRANSACTION_ISOLATION</varname> (<type>string</type>)</term> |
| 1055 | + <term><varname>DEFAULT_TRANSACTION_ISOLATION</varname> (<type>string</type>)</term> |
1017 | 1056 | <listitem>
|
1018 | 1057 | <para>
|
1019 | 1058 | Each SQL transaction has an isolation level, which can be
|
@@ -1201,6 +1240,19 @@ dynamic_library_path = '/usr/local/lib/postgresql:/home/my_project/lib:$libdir'
|
1201 | 1240 | </listitem>
|
1202 | 1241 | </varlistentry>
|
1203 | 1242 |
|
| 1243 | + <varlistentry> |
| 1244 | + <term><varname>PASSWORD_ENCRYPTION</varname> (<type>boolean</type>)</term> |
| 1245 | + <listitem> |
| 1246 | + <para> |
| 1247 | + When a password is specified in <command>CREATE USER</> or |
| 1248 | + <command>ALTER USER</> without writing either ENCRYPTED or |
| 1249 | + UNENCRYPTED, this flag determines whether the password is encrypted. |
| 1250 | + The default is off (do not encrypt the password), but this choice |
| 1251 | + may change in a future release. |
| 1252 | + </para> |
| 1253 | + </listitem> |
| 1254 | + </varlistentry> |
| 1255 | + |
1204 | 1256 | <varlistentry>
|
1205 | 1257 | <term><varname>TRANSFORM_NULL_EQUALS</varname> (<type>boolean</type>)</term>
|
1206 | 1258 | <listitem>
|
@@ -1285,7 +1337,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:/home/my_project/lib:$libdir'
|
1285 | 1337 | <listitem>
|
1286 | 1338 | <para>
|
1287 | 1339 | Specifies the amount of memory to be used by internal sorts
|
1288 |
| - and hashes before resorting to temporary disk files. The value |
| 1340 | + and hashes before switching to temporary disk files. The value |
1289 | 1341 | is specified in kilobytes, and defaults to 512 kilobytes. Note
|
1290 | 1342 | that for a complex query, several sorts and/or hashes might be
|
1291 | 1343 | running in parallel, and each one will be allowed to use as
|
@@ -1403,6 +1455,19 @@ dynamic_library_path = '/usr/local/lib/postgresql:/home/my_project/lib:$libdir'
|
1403 | 1455 | </listitem>
|
1404 | 1456 | </varlistentry>
|
1405 | 1457 |
|
| 1458 | + <varlistentry> |
| 1459 | + <term><varname>VACUUM_MEM</varname> (<type>integer</type>)</term> |
| 1460 | + <listitem> |
| 1461 | + <para> |
| 1462 | + Specifies the maximum amount of memory to be used by |
| 1463 | + <command>VACUUM</command> to keep track of to-be-reclaimed tuples. |
| 1464 | + The value is specified in kilobytes, and defaults to 8192 kilobytes. |
| 1465 | + Larger settings may improve the speed of vacuuming large tables |
| 1466 | + that have many deleted tuples. |
| 1467 | + </para> |
| 1468 | + </listitem> |
| 1469 | + </varlistentry> |
| 1470 | + |
1406 | 1471 | <varlistentry>
|
1407 | 1472 | <term><varname>VIRTUAL_HOST</varname> (<type>string</type>)</term>
|
1408 | 1473 | <listitem>
|
|
0 commit comments