*** pgsql/doc/src/sgml/libpq.sgml	2009/04/27 16:27:36	1.288
--- pgsql/doc/src/sgml/libpq.sgml	2009/05/28 20:02:10	1.289
***************
*** 1,4 ****
! <!-- $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.287 2009/04/24 14:10:41 mha Exp $ -->
  
  <chapter id="libpq">
   <title><application>libpq</application> - C Library</title>
--- 1,4 ----
! <!-- $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.288 2009/04/27 16:27:36 momjian Exp $ -->
  
  <chapter id="libpq">
   <title><application>libpq</application> - C Library</title>
***************
*** 64,69 ****
--- 64,79 ----
     whether a connection was successfully made before queries are sent
     via the connection object.
  
+    <warning>
+     <para>
+      On Unix, forking a process with open libpq connections can lead to
+      unpredictable results because the parent and child processes share
+      the same sockets and operating system resources.  For this reason,
+      such usage is not recommended, though doing an <function>exec</> from
+      the child process to load a new executable is safe.
+     </para>
+    </warning>
+ 
     <note>
      <para>
       On Windows, there is a way to improve performance if a single