| 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 |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-02-09 03:41:44 | Re: [PATCHES] date overflows |
| Previous Message | Michael Fuhr | 2006-02-08 22:50:05 | Re: BUG #2236: extremely slow to get unescaped bytea data |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-02-09 02:48:34 | Re: [HACKERS] Krb5 & multiple DB connections |
| Previous Message | Alvaro Herrera | 2006-02-08 13:46:59 | Re: BUG #2246: Bad malloc interactions: ecpg, openssl |