libpqxx
|
Descriptor of library's thread-safety model. More...
#include <util.hxx>
Public Attributes | |
bool | have_safe_strerror = true |
bool | safe_libpq |
Is the underlying libpq build thread-safe? More... | |
bool | safe_query_cancel = true |
bool | safe_result_copy = true |
bool | safe_kerberos |
Is Kerberos thread-safe? More... | |
std::string | description |
A human-readable description of any thread-safety issues. More... | |
Descriptor of library's thread-safety model.
This describes what the library knows about various risks to thread-safety.
std::string pqxx::thread_safety_model::description |
A human-readable description of any thread-safety issues.
Referenced by pqxx::describe_thread_safety().
bool pqxx::thread_safety_model::have_safe_strerror = true |
bool pqxx::thread_safety_model::safe_kerberos |
Is Kerberos thread-safe?
false
.If your application uses Kerberos, all accesses to libpqxx or Kerberos must be serialized. Confine their use to a single thread, or protect it with a global lock.
Referenced by pqxx::describe_thread_safety().
bool pqxx::thread_safety_model::safe_libpq |
Is the underlying libpq build thread-safe?
A "false"
here may mean one of two things: either the libpq build is not thread-safe, or it is a thread-safe build of an older version that did not offer thread-safety information.
In that case, the best fix is to rebuild libpqxx against (a thread-safe build of) a newer libpq version.
Referenced by pqxx::describe_thread_safety().
bool pqxx::thread_safety_model::safe_query_cancel = true |
bool pqxx::thread_safety_model::safe_result_copy = true |