"Andy Klosterman" <[EMAIL PROTECTED]> writes: > SPECULATION: Another possibility is that I misunderstand some aspect of > multi-threaded interactions with Postgres (I open uniquely named connections > to the DB for each thread of my test program). Maybe I need to have a > "lock" around the code that makes DB connections and make sure that only one > happens at a time (might be better handled within Postgres/SSL if that is > the case).
There could be some re-entrancy problem in the SSL connection startup code --- if you add such a lock, does it get more reliable? Also, did you remember to build PG with --enable-thread-safety ? regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org