|
1 | 1 | <!-- |
2 | | -$Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.124 2002/08/12 00:36:11 tgl Exp $ |
| 2 | +$Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.125 2002/08/15 14:26:15 momjian Exp $ |
3 | 3 | --> |
4 | 4 |
|
5 | 5 | <Chapter Id="runtime"> |
@@ -1293,71 +1293,11 @@ dynamic_library_path = '/usr/local/lib/postgresql:/home/my_project/lib:$libdir' |
1293 | 1293 | </varlistentry> |
1294 | 1294 |
|
1295 | 1295 | <varlistentry> |
1296 | | - <term><varname>SEARCH_PATH</varname> (<type>string</type>)</term> |
1297 | | - <indexterm><primary>search_path</></> |
1298 | | - <indexterm><primary>namespaces</></> |
| 1296 | + <term><varname>KRB_SERVER_KEYFILE</varname> (<type>string</type>)</term> |
1299 | 1297 | <listitem> |
1300 | 1298 | <para> |
1301 | | - This variable specifies the order in which namespaces are searched |
1302 | | -when an object (table, datatype, function, etc) is referenced by a |
1303 | | -simple name with no schema component. When there are objects of |
1304 | | -identical names in different namespaces, the one found first |
1305 | | -in the search path is used. An object that is not in any of the |
1306 | | -namespaces in the search path can only be referenced by specifying |
1307 | | -its containing namespace with a qualified (dotted) name. |
1308 | | - </para> |
1309 | | - |
1310 | | - <para> |
1311 | | - The value for search_path has to be a comma-separated |
1312 | | - list of namespace (schema) names. If one of the list items is |
1313 | | - the special value <literal>$user</literal>, then the namespace |
1314 | | -having the same name as the SESSION_USER is substituted, if there |
1315 | | -is such a namespace. (If not, <literal>$user</literal> is ignored.) |
1316 | | - </para> |
1317 | | - |
1318 | | - <para> |
1319 | | - The system catalog namespace, <literal>pg_catalog</>, is always |
1320 | | -searched, whether it is mentioned in the path or not. If it is |
1321 | | -mentioned in the path then it will be searched in the specified |
1322 | | -order. If <literal>pg_catalog</> is not in the path then it will |
1323 | | -be searched <emphasis>before</> searching any of the path items. |
1324 | | -It should also be noted that the temporary-table namespace, |
1325 | | -<literal>pg_temp_nnn</>, is implicitly searched before any of |
1326 | | -these. |
1327 | | - </para> |
1328 | | - |
1329 | | - <para> |
1330 | | - When objects are created without specifying a particular target |
1331 | | -namespace, they will be placed in the first namespace listed |
1332 | | -in the search path. An error is reported if the search path is |
1333 | | -empty. |
1334 | | - </para> |
1335 | | - |
1336 | | - <para> |
1337 | | - The default value for this parameter is |
1338 | | - <literal>'$user, public'</literal> (where the second part will be |
1339 | | -ignored if there is no namespace named <literal>public</>). |
1340 | | -This supports shared use of a database (where no users |
1341 | | -have private namespaces, and all share use of <literal>public</>), |
1342 | | -private per-user namespaces, and combinations of these. Other |
1343 | | -effects can be obtained by altering the default search path |
1344 | | -setting, either globally or per-user. |
1345 | | - </para> |
1346 | | - |
1347 | | - <para> |
1348 | | - By default, a newly created database will contain a world-writable |
1349 | | -namespace named <literal>public</>, but no private namespaces. |
1350 | | -The administrator may choose to restrict permissions on |
1351 | | -<literal>public</> or even remove it, if that suits his purposes. |
1352 | | - </para> |
1353 | | - |
1354 | | - <para> |
1355 | | - The current effective value of the search path can be examined |
1356 | | -via the SQL function <function>current_schemas()</>. This is not |
1357 | | -quite the same as examining the value of |
1358 | | -<varname>search_path</varname>, since <function>current_schemas()</> |
1359 | | -shows how the requests appearing in <varname>search_path</varname> |
1360 | | -were resolved. |
| 1299 | + Sets the location of the Kerberos server key file. See |
| 1300 | + <xref linkend="kerberos-auth"> for details. |
1361 | 1301 | </para> |
1362 | 1302 | </listitem> |
1363 | 1303 | </varlistentry> |
@@ -1416,16 +1356,6 @@ dynamic_library_path = '/usr/local/lib/postgresql:/home/my_project/lib:$libdir' |
1416 | 1356 | </listitem> |
1417 | 1357 | </varlistentry> |
1418 | 1358 |
|
1419 | | - <varlistentry> |
1420 | | - <term><varname>KRB_SERVER_KEYFILE</varname> (<type>string</type>)</term> |
1421 | | - <listitem> |
1422 | | - <para> |
1423 | | - Sets the location of the Kerberos server key file. See |
1424 | | - <xref linkend="kerberos-auth"> for details. |
1425 | | - </para> |
1426 | | - </listitem> |
1427 | | - </varlistentry> |
1428 | | - |
1429 | 1359 | <varlistentry> |
1430 | 1360 | <term><varname>LC_MESSAGES</varname> (<type>string</type>)</term> |
1431 | 1361 | <listitem> |
@@ -1598,6 +1528,76 @@ dynamic_library_path = '/usr/local/lib/postgresql:/home/my_project/lib:$libdir' |
1598 | 1528 | </listitem> |
1599 | 1529 | </varlistentry> |
1600 | 1530 |
|
| 1531 | + <varlistentry> |
| 1532 | + <term><varname>SEARCH_PATH</varname> (<type>string</type>)</term> |
| 1533 | + <indexterm><primary>search_path</></> |
| 1534 | + <indexterm><primary>namespaces</></> |
| 1535 | + <listitem> |
| 1536 | + <para> |
| 1537 | + This variable specifies the order in which namespaces are searched |
| 1538 | +when an object (table, datatype, function, etc) is referenced by a |
| 1539 | +simple name with no schema component. When there are objects of |
| 1540 | +identical names in different namespaces, the one found first |
| 1541 | +in the search path is used. An object that is not in any of the |
| 1542 | +namespaces in the search path can only be referenced by specifying |
| 1543 | +its containing namespace with a qualified (dotted) name. |
| 1544 | + </para> |
| 1545 | + |
| 1546 | + <para> |
| 1547 | + The value for search_path has to be a comma-separated |
| 1548 | + list of namespace (schema) names. If one of the list items is |
| 1549 | + the special value <literal>$user</literal>, then the namespace |
| 1550 | +having the same name as the SESSION_USER is substituted, if there |
| 1551 | +is such a namespace. (If not, <literal>$user</literal> is ignored.) |
| 1552 | + </para> |
| 1553 | + |
| 1554 | + <para> |
| 1555 | + The system catalog namespace, <literal>pg_catalog</>, is always |
| 1556 | +searched, whether it is mentioned in the path or not. If it is |
| 1557 | +mentioned in the path then it will be searched in the specified |
| 1558 | +order. If <literal>pg_catalog</> is not in the path then it will |
| 1559 | +be searched <emphasis>before</> searching any of the path items. |
| 1560 | +It should also be noted that the temporary-table namespace, |
| 1561 | +<literal>pg_temp_nnn</>, is implicitly searched before any of |
| 1562 | +these. |
| 1563 | + </para> |
| 1564 | + |
| 1565 | + <para> |
| 1566 | + When objects are created without specifying a particular target |
| 1567 | +namespace, they will be placed in the first namespace listed |
| 1568 | +in the search path. An error is reported if the search path is |
| 1569 | +empty. |
| 1570 | + </para> |
| 1571 | + |
| 1572 | + <para> |
| 1573 | + The default value for this parameter is |
| 1574 | + <literal>'$user, public'</literal> (where the second part will be |
| 1575 | +ignored if there is no namespace named <literal>public</>). |
| 1576 | +This supports shared use of a database (where no users |
| 1577 | +have private namespaces, and all share use of <literal>public</>), |
| 1578 | +private per-user namespaces, and combinations of these. Other |
| 1579 | +effects can be obtained by altering the default search path |
| 1580 | +setting, either globally or per-user. |
| 1581 | + </para> |
| 1582 | + |
| 1583 | + <para> |
| 1584 | + By default, a newly created database will contain a world-writable |
| 1585 | +namespace named <literal>public</>, but no private namespaces. |
| 1586 | +The administrator may choose to restrict permissions on |
| 1587 | +<literal>public</> or even remove it, if that suits his purposes. |
| 1588 | + </para> |
| 1589 | + |
| 1590 | + <para> |
| 1591 | + The current effective value of the search path can be examined |
| 1592 | +via the SQL function <function>current_schemas()</>. This is not |
| 1593 | +quite the same as examining the value of |
| 1594 | +<varname>search_path</varname>, since <function>current_schemas()</> |
| 1595 | +shows how the requests appearing in <varname>search_path</varname> |
| 1596 | +were resolved. |
| 1597 | + </para> |
| 1598 | + </listitem> |
| 1599 | + </varlistentry> |
| 1600 | + |
1601 | 1601 | <varlistentry> |
1602 | 1602 | <term><varname>STATEMENT_TIMEOUT</varname> (<type>integer</type>)</term> |
1603 | 1603 | <listitem> |
|