Re: libpq is not thread safe

Bruce Momjian wrote:
> > Another advantage of atfork handler is that you can close all open
> > connection and clean resource (similar to what pkcs11 library does). But
> > at this moment libpq does not keep list of open connections and atfork
> > handler works only with pthreads.
> > 
> > > I think writing code to deal with this for the ssl_config mutex is entirely a waste
> > > of time.
> > 
> > yeah, I prefer to document it together how to deal with fork() and
> > sessions.
> 
> Done, patch attached and applied.

I went with a <warning> because it seemed most appropriate, but it looks
very large:
http://developer.postgresql.org/pgdocs/postgres/libpq-connect.html

Should it be a notice?

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +