| From: | mlw <pgsql(at)mohawksoft(dot)com> |
|---|---|
| To: | Greg Copeland <greg(at)CopelandConsulting(dot)Net> |
| Cc: | PostgresSQL Hackers Mailing List <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Memory leaks |
| Date: | 2002-10-29 11:11:37 |
| Message-ID: | 3DBE6CE9.5090301@mohawksoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Greg Copeland wrote:
>I've started playing a little with Postgres to determine if there were
>memory leaks running around. After some very brief checking, I'm
>starting[1] to think that the answer is yes. Has anyone already gone
>through a significant effort to locate and eradicate memory leaks? Is
>this done periodically? If so, what tools are others using? I'm
>currently using dmalloc for my curiosity.
>
>[1] Not sure yet as I'm really wanting to find culumative leaks rather
>than one shot allocations which are simply never freed prior to process
>termination.
>
While all leaks should be fixed, obviously, this is one of the "good"
things in the parennial "Thread vs process" argument for processes.
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pedro Miguel Frazao Fernandes Ferreira | 2002-10-29 11:34:58 | float output precision questions |
| Previous Message | Larry Rosenman | 2002-10-29 10:44:14 | good news: FreeBSD 4.7: all passed (with Bruce's resultmap change). |