Re: --enable-thread-safety bug

From: Michael Meskes <meskes(at)postgresql(dot)org>
To: Steve Clark <sclark(at)netwolves(dot)com>
Cc: Martijn van Oosterhout <kleptog(at)svana(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql <pgsql-general(at)postgresql(dot)org>
Subject: Re: --enable-thread-safety bug
Date: 2008-03-22 20:11:12
Message-ID: 20080322201112.GA5389@feivel.credativ.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sat, Mar 22, 2008 at 12:51:30PM -0400, Steve Clark wrote:
> My program had no threads - as I pointed out if I change the default
> Makefile in the FreeBSD ports
> system to not enable thread safety my programs runs just fine for days
> on end. It appears to me
> without any kind of close examination that there is a memory leak in the
> ecpg library when enable
> thread safety is turned on.

There are just a few variables covered by ENABLE_THREAD_SAFETY. I wonder
how the program manages to spend so much time allocating memory to eat
all of it. Could you give us some more info about your source code? Do
you use descriptors? Auto allocating?

Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes(at)jabber(dot)org
Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL!

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alvaro Herrera 2008-03-22 20:47:56 Re: dynamically generated SQL and planner/performance
Previous Message George Nychis 2008-03-22 18:48:07 help optimizing query