|
|
|
|
@ -1,4 +1,4 @@ |
|
|
|
|
<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.109 2007/02/08 03:56:42 momjian Exp $ --> |
|
|
|
|
<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.110 2007/02/08 15:46:03 momjian Exp $ --> |
|
|
|
|
|
|
|
|
|
<chapter Id="runtime-config"> |
|
|
|
|
<title>Server Configuration</title> |
|
|
|
|
@ -990,6 +990,17 @@ SET ENABLE_SEQSCAN TO OFF; |
|
|
|
|
libraries that will be used in most sessions. |
|
|
|
|
</para> |
|
|
|
|
|
|
|
|
|
<note> |
|
|
|
|
<para> |
|
|
|
|
On Windows hosts, preloading a library at server start will not reduce |
|
|
|
|
the time required to start each new server process; each server process |
|
|
|
|
will re-load all preload libraries. However, <varname>shared_preload_libraries |
|
|
|
|
</varname> is still useful on Windows hosts because some shared libraries may |
|
|
|
|
need to perform certain operations that only take place at postmaster start |
|
|
|
|
(for example, a shared library may need to reserve lightweight locks |
|
|
|
|
or shared memory and you can't do that after the postmaster has started). |
|
|
|
|
</para> |
|
|
|
|
</note> |
|
|
|
|
<para> |
|
|
|
|
If a specified library is not found, |
|
|
|
|
the server will fail to start. |
|
|
|
|
|