Re: [HACKERS] Re: memory leak with Abort Transaction

From: jwieck(at)debis(dot)com (Jan Wieck)
To: takehi-s(at)ascii(dot)co(dot)jp (SHIOZAKI Takehiko)
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Re: memory leak with Abort Transaction
Date: 1998-11-26 13:01:42
Message-ID: m0zj13G-000EBfC@orion.SAPserv.Hamburg.dsh.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

SHIOZAKI Takehiko wrote:

>
> Hello!
>
> Releasing 6.4.1 is a good news.
> But would you confirm the following "memory leak" problem?
> It is reproducable on 6.4 (FreeBSD 2.2.7-RELEASE).

It's an far too old problem. And as far as I remember, there
are different locations in the code causing it.

One place I remember well. It's in the tcop mainloop in
PostgresMain(). The querytree list is malloc()'ed (there and
in the parser) and free()'d after the query is processed -
except the processing of the queries bails out with elog().
In that case it never runs over the free() because the
longjmp() kick's it back to the beginning of the loop.

Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#======================================== jwieck(at)debis(dot)com (Jan Wieck) #

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Meskes 1998-11-26 20:25:39 corba
Previous Message SHIOZAKI Takehiko 1998-11-26 12:40:19 Re: memory leak with Abort Transaction