Document that forking while having open libpq connections is not

advised.

diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml
index 44b117e4cdbef1e2b4f9ef02d6ec8f04bd29304e..85ba6dadd1ddfed2e8ddfe19cb5e2866727261f1 100644 (file)
--- a/doc/src/sgml/libpq.sgml
+++ b/doc/src/sgml/libpq.sgml
@@ -1,4 +1,4 @@
-
+
 
 
  <application>libpq</application> - C Library
@@ -64,6 +64,16 @@
    whether a connection was successfully made before queries are sent
    via the connection object.
 
+   
+    
+     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 exec from
+     the child process to load a new executable is safe.
+    
+   
+
    
     
      On Windows, there is a way to improve performance if a single