|
1 | 1 | <!-- |
2 | | -$PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.151 2004/04/20 01:11:49 momjian Exp $ |
| 2 | +$PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.152 2004/04/24 00:14:28 momjian Exp $ |
3 | 3 | --> |
4 | 4 |
|
5 | 5 | <chapter id="libpq"> |
@@ -3623,7 +3623,9 @@ If the permissions are less strict than this, the file will be ignored. |
3623 | 3623 | addition, you might need to use additional compiler command-line |
3624 | 3624 | options when you compile your application code. Refer to your |
3625 | 3625 | system's documentation for information about how to build |
3626 | | -thread-enabled applications. |
| 3626 | +thread-enabled applications, or look in |
| 3627 | +<filename>src/Makefile.global</filename> for <literal>PTHREAD_CFLAGS</> |
| 3628 | +and <literal>PTHREAD_LIBS</>. |
3627 | 3629 | </para> |
3628 | 3630 |
|
3629 | 3631 | <para> |
@@ -3674,6 +3676,14 @@ its own <literal>SIGPIPE</> signal handler, it should call |
3674 | 3676 | <literal>SIGPIPE</> signal. This function is available in both |
3675 | 3677 | thread-safe and non-thread-safe versions of <application>libpq</>. |
3676 | 3678 | </para> |
| 3679 | + |
| 3680 | +<para> |
| 3681 | +If you experience problems with threaded applications, run |
| 3682 | +the program in <filename>src/tools/thread</> to see if your |
| 3683 | +platform has thread-unsafe functions. This program is run |
| 3684 | +by <filename>configure</filename>, but for binary distributions |
| 3685 | +your library might not match the library used to build the binaries. |
| 3686 | +</para> |
3677 | 3687 | </sect1> |
3678 | 3688 |
|
3679 | 3689 |
|
|