PostgreSQL developers. 222 Chapter 14. Installation Instructions --enable-thread-safety Make the client libraries thread-safe. This allows concurrent threads in libpq and ECPG programs to safely control These two functions are used to open a connection to a database server such that your appli- cation’s thread of execution is not blocked on remote I/O whilst doing so. The point of this approach is that the *PQoidStatus(const PGresult *res); This function is deprecated in favor of PQoidValue. It is not thread-safe. 27.3.4. Escaping Strings for Inclusion in SQL Commands PQescapeString escapes a string for

platform, please report the problem to the PostgreSQL developers. --enable-thread-safety Make the client libraries thread-safe. This allows concurrent threads in libpq and ECPG pro- grams to safely control These two functions are used to open a connection to a database server such that your application’s thread of execution is not blocked on remote I/O whilst doing so. The point of this approach is that the *PQoidStatus(const PGresult *res); This function is deprecated in favor of PQoidValue. It is not thread-safe. 374 Chapter 27. libpq - C Library 27.3.4. Escaping Strings for Inclusion in SQL Commands

platform, please report the problem to the PostgreSQL developers. --enable-thread-safety Make the client libraries thread-safe. This allows concurrent threads in libpq and ECPG pro- grams to safely control These two functions are used to open a connection to a database server such that your application’s thread of execution is not blocked on remote I/O whilst doing so. The point of this approach is that the *PQoidStatus(const PGresult *res); This function is deprecated in favor of PQoidValue. It is not thread-safe. 28.3.4. Escaping Strings for Inclusion in SQL Commands PQescapeStringConn escapes a string

platform, please report the problem to the PostgreSQL developers. --enable-thread-safety Make the client libraries thread-safe. This allows concurrent threads in libpq and ECPG pro- grams to safely control These two functions are used to open a connection to a database server such that your application’s thread of execution is not blocked on remote I/O whilst doing so. The point of this approach is that the *PQoidStatus(const PGresult *res); This function is deprecated in favor of PQoidValue. It is not thread-safe. 28.3.4. Escaping Strings for Inclusion in SQL Commands PQescapeString escapes a string for

platform, please report the problem to the PostgreSQL developers. --enable-thread-safety Make the client libraries thread-safe. This allows concurrent threads in libpq and ECPG pro- grams to safely control These two functions are used to open a connection to a database server such that your application’s thread of execution is not blocked on remote I/O whilst doing so. The point of this approach is that the *PQoidStatus(const PGresult *res); This function is deprecated in favor of PQoidValue. It is not thread-safe. 439 Chapter 29. libpq - C Library 29.3.4. Escaping Strings for Inclusion in SQL Commands

platform, please report the problem to the PostgreSQL developers. --enable-thread-safety Make the client libraries thread-safe. This allows concurrent threads in libpq and ECPG pro- grams to safely control These two functions are used to open a connection to a database server such that your application’s thread of execution is not blocked on remote I/O whilst doing so. The point of this approach is that the *PQoidStatus(const PGresult *res); This function is deprecated in favor of PQoidValue. It is not thread-safe. 439 Chapter 29. libpq - C Library 29.3.4. Escaping Strings for Inclusion in SQL Commands

platform, please report the problem to the PostgreSQL developers. --enable-thread-safety Make the client libraries thread-safe. This allows concurrent threads in libpq and ECPG programs to safely control These two functions are used to open a connection to a database server such that your appli- cation’s thread of execution is not blocked on remote I/O whilst doing so. The point of this approach is that the *PQoidStatus(const PGresult *res); This function is deprecated in favor of PQoidValue. It is not thread-safe. 30.3.4. Escaping Strings for Inclusion in SQL Commands PQescapeStringConn escapes a string

platform, please report the problem to the PostgreSQL developers. --enable-thread-safety Make the client libraries thread-safe. This allows concurrent threads in libpq and ECPG pro- grams to safely control These two functions are used to open a connection to a database server such that your application’s thread of execution is not blocked on remote I/O whilst doing so. The point of this approach is that the *PQoidStatus(const PGresult *res); This function is deprecated in favor of PQoidValue. It is not thread-safe. 30.3.4. Escaping Strings for Inclusion in SQL Commands PQescapeStringConn escapes a string

6. C99 Issues with the 7.1.1b Feature Supplement .........................356 15.8.6.7. --enable-thread-safety and UnixWare .............................356 15.8.7. Solaris .......................... platform, please report the problem to the PostgreSQL developers. --enable-thread-safety Make the client libraries thread-safe. This allows concurrent threads in libpq and ECPG programs to safely control change in the 7.1.2(8.0.0) compiler and beyond. 15.8.6.7. --enable-thread-safety and UnixWare If you use the configure option --enable-thread-safety, you must use -Kpthread on all libpq-using programs. libpq

Issues with the 7.1.1b Feature Supplement ................................377 15.8.6.7. --enable-thread-safety and UnixWare ....................................378 15.8.7. Solaris ................... platform, please report the problem to the PostgreSQL developers. --enable-thread-safety Make the client libraries thread-safe. This allows concurrent threads in libpq and ECPG pro- grams to safely control change in the 7.1.2(8.0.0) compiler and beyond. 15.8.6.7. --enable-thread-safety and UnixWare If you use the configure option --enable-thread-safety, you must use -Kpthread on all libpq- using programs. libpq