Re: Backend memory leakage when inserting - Mailing list pgsql-general

From Dennis Gearon
Subject Re: Backend memory leakage when inserting
Date
Msg-id 3EAE97D1.1050000@cvc.net
Whole thread Raw
In response to Re: Backend memory leakage when inserting  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
a lot of people have seen JAVA leaks and ODBC leaks. Are you using those?

Tom Lane wrote:
> g.hintermayer@inode.at (Gerhard Hintermayer) writes:
>
>>I'm currently using 7.3.1 (linux 2.2.17) and noticed a memory leakage
>>in the backend when I do lots of inserts.
>
>
> Unless you provide enough info for someone else to duplicate the
> problem, it's going to be hard to say if it's been fixed or not.
>
> I see only one memory-leak patch in the CVS logs, and it's for plpgsql:
>
> 2003-03-02 15:45  tgl
>
>     * src/pl/plpgsql/src/pl_exec.c (REL7_3_STABLE): Repair memory leak
>     introduced by recent change to make SPI return a tupdesc even with
>     zero tuples returned: some plpgsql routines assumed they didn't
>     need to do SPI_freetuptable() after retrieving no tuples.
>
> This is post-7.3.2 ...
>
>             regards, tom lane
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
>


pgsql-general by date:

Previous
From: Dennis Gearon
Date:
Subject: Re: Importing from Access 2000?
Next
From: Richard Huxton
Date:
Subject: Re: Importing from Access 2000?