mirror of
https://git.postgresql.org/git/postgresql.git
synced 2025-01-18 18:44:06 +08:00
Document that forking while having open libpq connections is not
advised.
This commit is contained in:
parent
2e6107cb62
commit
400fb19a30
@ -1,4 +1,4 @@
|
||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.288 2009/04/27 16:27:36 momjian Exp $ -->
|
||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.289 2009/05/28 20:02:10 momjian Exp $ -->
|
||||
|
||||
<chapter id="libpq">
|
||||
<title><application>libpq</application> - C Library</title>
|
||||
@ -64,6 +64,16 @@
|
||||
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
|
||||
|
Loading…
Reference in New Issue
Block a user