-<!-- $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>
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.
*
*
* IDENTIFICATION
- * $PostgreSQL: pgsql/src/backend/postmaster/postmaster.c,v 1.517 2007/02/07 16:44:48 tgl Exp $
+ * $PostgreSQL: pgsql/src/backend/postmaster/postmaster.c,v 1.518 2007/02/08 15:46:04 momjian Exp $
*
* NOTES
*
secure_initialize();
#endif
+ /*
+ * process any libraries that should be preloaded at postmaster start
+ *
+ * NOTE: we have to re-load the shared_preload_libraries here because
+ * this backend is not fork()ed so we can't inherit any shared
+ * libraries / DLL's from our parent (the postmaster).
+ */
+ process_shared_preload_libraries();
+
/*
* Perform additional initialization and client authentication.
*