Re: memory leaks fixed?

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Nick T <ntaylor84(at)earthlink(dot)net>
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: Re: memory leaks fixed?
Date: 2001-04-08 11:05:38
Message-ID: Pine.LNX.4.30.0104081258230.1236-100000@peter.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Nick T writes:

> Just finished reading all of the comments at
>
> http://openacs.org/philosophy/why-not-mysql.html
>
> and became concerned about the comments regarding severe memory leaks with
> PostgreSQL. Is this true? Have they been fixed? Are there any
> workarounds?

There are certain queries that require a seemingly unproportional amount
of memory. Up until verion 7.0, memory in the server was not recovered
until the end of the transaction, so it was possible to run out of memory
when it should have been avoidable. This is technically not a memory
leak, just a less than optimal use of resources. However, because of the
way malloc/sbrk work, this memory is no longer available to the operating
system, so it looks like a memory leak.

7.1 uses a better technique to handle the allocated memory, which should
fix most of these cases. In any case it should be possible to rewrite the
queries, but there is no general procedure on how to do that.

--
Peter Eisentraut peter_e(at)gmx(dot)net http://yi.org/peter-e/

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Peter Eisentraut 2001-04-08 11:15:37 Re: [GENERAL] Better Features document?
Previous Message Marek Pętlicki 2001-04-08 10:55:30 Re: updates way slower than selects?