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