Skip site navigation (1) Skip section navigation (2)

Re: BUG #2246: Bad malloc interactions: ecpg, openssl

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Andy Klosterman" <andrew5(at)ece(dot)cmu(dot)edu>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2246: Bad malloc interactions: ecpg, openssl
Date: 2006-02-09 01:10:34
Message-ID: 21904.1139447434@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-patches
"Andy Klosterman" <andrew5(at)ece(dot)cmu(dot)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

In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2006-02-09 03:41:44
Subject: Re: [PATCHES] date overflows
Previous:From: Michael FuhrDate: 2006-02-08 22:50:05
Subject: Re: BUG #2236: extremely slow to get unescaped bytea data

pgsql-patches by date

Next:From: Tom LaneDate: 2006-02-09 02:48:34
Subject: Re: [HACKERS] Krb5 & multiple DB connections
Previous:From: Alvaro HerreraDate: 2006-02-08 13:46:59
Subject: Re: BUG #2246: Bad malloc interactions: ecpg, openssl

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group