Re: BUG #2246: Bad malloc interactions: ecpg, openssl - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #2246: Bad malloc interactions: ecpg, openssl
Date
Msg-id 21904.1139447434@sss.pgh.pa.us
Whole thread Raw
In response to BUG #2246: Bad malloc interactions: ecpg, openssl  ("Andy Klosterman" <andrew5@ece.cmu.edu>)
Responses Re: BUG #2246: Bad malloc interactions: ecpg, openssl
List pgsql-bugs
"Andy Klosterman" <andrew5@ece.cmu.edu> 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

pgsql-bugs by date:

Previous
From: Michael Fuhr
Date:
Subject: Re: BUG #2236: extremely slow to get unescaped bytea data
Next
From: Tom Lane
Date:
Subject: Re: [PATCHES] date overflows